headers
Offray Vladimir Luna Cárdenas | 3 Jun 2008 18:48
Picon
Favicon

Ongoing translation of A TeXmacs Tutorial by Henri

Hi all,

I have just started the translation of A TeXmacs Tutorial in 
http://www.ags.uni-sb.de/~henri/texmacs/aTeXmacsTutorial.pdf. Some time 
ago I asked for the TeXmacs sources for this tuturial, because I know is 
easier to translate the docs in this way but I get no response. I have 
created a FreeHg repository for version control of this document at:

http://freehg.org/u/offray/texmacsdocs/

I'm a newbie also on Mercurial and FreeHg, so I don't know if this has a 
public view. FreeHg is for OSI an Creative Commons covered projects. I 
have also asked previously which is the License of the tutorial, but 
being for a GPL project I hope that this will be also under a compatible 
license and there is no problem for that.

I see that the tutorial mixes explanations of how to get a format with 
the underline tagging for that, which is very useful. I have tried to 
copy and paste the underlying markup in the translation, but any time I 
tried I get the text with the format applied, not the raw text. There is 
any way to get this?

Is fine to advance with this Spanish translation or I have not 
permissions to make this? (In that case I will keep only for personal 
use without public permissions) Which is the License of the original doc?

Thanks,

Offray
(Continue reading)

Permalink | Reply | 2 comments |
headers
Stephan Mucha | 4 Jun 2008 10:27
Picon
Favicon

TeXmacs with Qt GUI

What's the status of "QTeXmacs"? Is it possible to get a snapshot of
the source?

--

-- 
Thanks!
Stephan
Permalink | Reply | 1 comment |
headers
Andreas Körner | 5 Jun 2008 20:03
Picon
Gravatar

Compiling TexMacs on OSX

Hi at all,

some time ago I wrote the same Problem to the TexMacs Userlist:

I try to compile TexMacs on OSX:

i've installed my Mac completely new this day (10.4 Tiger)
installed fink
installed, guile, guile-dev via fink

Now I tried to complie the current TeXmacs from CVS (with --enable- 
cocoa) and the following errors appeard on the screen:

./Plugins/Cocoa/aqua_gui.h:106: warning: 'class aqua_gui_rep' has  
virtual functions but non-virtual destructor
./Plugins/Cocoa/TMView.mm: In function 'void -[TMView insertText:] 
(TMView*, objc_selector*, objc_object*)':
./Plugins/Cocoa/TMView.mm:518: warning: comparison between signed and  
unsigned integer expressions
./Plugins/Cocoa/TMView.mm: At global scope:
./Plugins/Cocoa/TMView.mm:556: error: expected type-specifier before  
'NSInteger'
./Plugins/Cocoa/TMView.mm:556: error: expected `)' before 'NSInteger'
./Plugins/Cocoa/TMView.mm: In function '<typeprefixerror>-[TMView  
NSInteger](TMView*, objc_selector*)':
./Plugins/Cocoa/TMView.mm:556: error: return type '<type error>' is  
incomplete
./Plugins/Cocoa/TMView.mm:556: confused by earlier errors, bailing out
make[1]: *** [Objects/TMView.o] Error 1
make: *** [TEXMACS] Error 2
(Continue reading)

Permalink | Reply | 17 comments |
headers
Andreas Körner | 9 Jun 2008 17:02
Picon
Gravatar

Re: Compiling TexMacs on OSX

Ok, 

I got It compiled for Myself:

I used the following tricks:

first at all: 

fink -b install texmacs  - But I thinks thats not needed

in src/Plugin/Cocoa:

#define NSInteger int
#define NSUInteger uint

I think thats some kind of stupid but as NSInteger and NSUInteger 
where not defined in Apples Docs I found this as a good workaround 
because NSInteger was not defined but used.

 Next I found that imlib2.hpp needed X11/... this is in the Apple SDK, but not in the Include path
As I didn't know how to change the Include path I

ln -s /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/include/X11 /sw/include/X11

than a simple

./configure --enable-cocoa
make
make BUNDLE #   or   make DISKIMAGE

works (but it's VERY unstable at the moment)

Ok ... how can I help to improve the mac port?

greetings

andi
_______________________________________________
Texmacs-dev mailing list
Texmacs-dev <at> gnu.org
http://lists.gnu.org/mailman/listinfo/texmacs-dev
Permalink | Reply | 16 comments |
headers
apostolos1975 | 9 Jun 2008 18:26
Picon

Hlink and pdf or ps


Hi all,

I am trying to export a pdf file that contains for example:

<hlink|cnn|http://www.cnn.com>

the result is plain text (the word cnn) not the link the I want it to be. If
I export to html everything is ok but not in pdf or ps. I have search alot
but couldnt find an answer. 

Any suggestion? Thanks in advance

Apostolos
--

-- 
View this message in context: http://www.nabble.com/Hlink-and-pdf-or-ps-tp17736551p17736551.html
Sent from the Gnu - Texmacs - Dev mailing list archive at Nabble.com.
Permalink | Reply | 1 comment |
headers
m.gubinelli | 11 Jun 2008 16:57
Picon

Re: Compiling TexMacs on OSX

Hi,

On Jun 9, 2008, at 5:02 PM, Andreas Körner wrote:

Ok, 

I got It compiled for Myself:

I used the following tricks:

first at all: 

fink -b install texmacs  - But I thinks thats not needed

in src/Plugin/Cocoa:

#define NSInteger int
#define NSUInteger uint

I think thats some kind of stupid but as NSInteger and NSUInteger 
where not defined in Apples Docs I found this as a good workaround 
because NSInteger was not defined but used.


I think NSInteger has been introduced in 10.5. I developer the cocoa port under Leopard (at least in the last times) and I hadn't the opportunity to test it on 10.4. 


 Next I found that imlib2.hpp needed X11/... this is in the Apple SDK, but not in the Include path
As I didn't know how to change the Include path I

ln -s /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/include/X11 /sw/include/X11

than a simple

./configure --enable-cocoa
make
make BUNDLE #   or   make DISKIMAGE

works (but it's VERY unstable at the moment)

Ok ... how can I help to improve the mac port?


the port is in a very early stage. My first goal has been to implement roughly the basic stuff, also to get acquainted with the source code. Joris has made a very nice work in separating the different layers of the GUI and it has been not so difficult to make TeXmacs run natively under cocoa. 
However there are many weak points:
1) the rendering mechanism which keeps the UI up to date while typing is not as smooth as in the X11 version. In particular at the moment the shadow rendering mechanism is virtually disabled (in the sense that the shadow drawable is actually the real drawable)
2) the support for the keyboard is primitive. Mac keyboard allows very complex patterns (like the key sequence required to produce chars like î on english keyboards). We must take inspiration from other ports to have a sensible way of doing it. (e.g. look at the cocoa port of Emacs).
3) all widgets for opening, saving, printing must be correctly implemented. At the moment they are just mock up implemented with standard parts which does not fit very well the logic of texmacs.
4) menus are working but improvements should be possible (caching?, better structure for the code,...)
5) better handling of fonts, possibility to use directly system fonts (or open-type versions) instead of the bitmap fonts created by freetype or pk fonts
6) there are problems with images 

These are the priorities as far as I'm concerned. For personal reasons I'm not able at the moment to spend much time on the port, but I hope to do so within some months. But I would be glad if somebody would like to join the effort. At the moment the cocoa code base is not very large and it is a good moment to join the project since it will not take much effort to have a complete understanding of the port (and is also an easy way to start understanding the TeXmacs codebase).

Best,
Massimiliano Gubinelli






greetings

andi
_______________________________________________
Texmacs-dev mailing list

_______________________________________________
Texmacs-dev mailing list
Texmacs-dev <at> gnu.org
http://lists.gnu.org/mailman/listinfo/texmacs-dev
Permalink | Reply | 15 comments |
headers
Andreas Körner | 11 Jun 2008 18:13
Picon
Gravatar

Re: Compiling TexMacs on OSX

Hi,

Additionally I found these bugs:

- TexMacs crashes on some special Symbols like "¡ ß" etc.
- The Drawing tools has redraw Errors.
- Open a Document ask if I would like to overwrite it...

The time I can spend on texmacs is also very limited... And additionally I did never write a Cocoa app... just some others.
But I will see what I can do.

I think it would be a good thing to tell the world of this coca port. I think this will automatically "generate" some helping hands... the hard part of the work is done, in my oppinion. the other things are little steps.

Do you also like patches instead of cvs? 
For first I would add the NSInteger things... 
(But ask me not WHEN the this patch will arrive...)

greetings
andi




Am 11.06.2008 um 16:57 schrieb m.gubinelli <at> gmail.com:

Hi,

On Jun 9, 2008, at 5:02 PM, Andreas Körner wrote:

Ok, 

I got It compiled for Myself:

I used the following tricks:

first at all: 

fink -b install texmacs  - But I thinks thats not needed

in src/Plugin/Cocoa:

#define NSInteger int
#define NSUInteger uint

I think thats some kind of stupid but as NSInteger and NSUInteger 
where not defined in Apples Docs I found this as a good workaround 
because NSInteger was not defined but used.


I think NSInteger has been introduced in 10.5. I developer the cocoa port under Leopard (at least in the last times) and I hadn't the opportunity to test it on 10.4. 


 Next I found that imlib2.hpp needed X11/... this is in the Apple SDK, but not in the Include path
As I didn't know how to change the Include path I

ln -s /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/include/X11 /sw/include/X11

than a simple

./configure --enable-cocoa
make
make BUNDLE #   or   make DISKIMAGE

works (but it's VERY unstable at the moment)

Ok ... how can I help to improve the mac port?


the port is in a very early stage. My first goal has been to implement roughly the basic stuff, also to get acquainted with the source code. Joris has made a very nice work in separating the different layers of the GUI and it has been not so difficult to make TeXmacs run natively under cocoa. 
However there are many weak points:
1) the rendering mechanism which keeps the UI up to date while typing is not as smooth as in the X11 version. In particular at the moment the shadow rendering mechanism is virtually disabled (in the sense that the shadow drawable is actually the real drawable)
2) the support for the keyboard is primitive. Mac keyboard allows very complex patterns (like the key sequence required to produce chars like î on english keyboards). We must take inspiration from other ports to have a sensible way of doing it. (e.g. look at the cocoa port of Emacs).
3) all widgets for opening, saving, printing must be correctly implemented. At the moment they are just mock up implemented with standard parts which does not fit very well the logic of texmacs.
4) menus are working but improvements should be possible (caching?, better structure for the code,...)
5) better handling of fonts, possibility to use directly system fonts (or open-type versions) instead of the bitmap fonts created by freetype or pk fonts
6) there are problems with images 

These are the priorities as far as I'm concerned. For personal reasons I'm not able at the moment to spend much time on the port, but I hope to do so within some months. But I would be glad if somebody would like to join the effort. At the moment the cocoa code base is not very large and it is a good moment to join the project since it will not take much effort to have a complete understanding of the port (and is also an easy way to start understanding the TeXmacs codebase).

Best,
Massimiliano Gubinelli






greetings

andi
_______________________________________________
Texmacs-dev mailing list

_______________________________________________
Texmacs-dev mailing list

_______________________________________________
Texmacs-dev mailing list
Texmacs-dev <at> gnu.org
http://lists.gnu.org/mailman/listinfo/texmacs-dev
Permalink | Reply | 0 comments |
headers
Kostas Oikonomou | 12 Jun 2008 23:47
Picon

some fixes for the latex converter

(I sent this to contact <at> texmacs.org on June 1, and I am reposting it 
here since I did not receive any reply.)

Hello,

I have a couple of improvements to the Latex converter for
TeXmacs 1.0.6.14.

The first has to do with exporting the \S command, which
currently doesn't work: TeXmacs puts an octal 237 character
in the .tex file, which latex ignores.  I made the following
fix in file tmtex.scm:

(define (tmtex-text-list l)
...
     ((== c #\26) (tmtex-text-sub "---" l))
     ; See progs/texmacs/keyboard/latex-kbd.scm, line 169:
     ((== c #\237) (tmtex-text-sub "\\S" l))
...

The other fix allows TeXmacs to use Latex's \bigl, \bigr,
etc. commands when exporting large delimiter constructs such
as <left|(|2>, which right now are all exported as \left(, etc.
So in the same file, I have rewritten tmtex-left and
tmtex-right:

; Parses TeXmacs delimiter constructs like <left|[|3> or
<left|)>.
(define (tmtex-left l)
   (let (
         (s (car l))
         (n (if (> (length l) 1) (string->number (cadr l)) 0))
        )
     (list (string->symbol
       (cond
         ((nstring? (car l)) "left.")
         ((in? s '("(" ")" "[" "]" "{" "}" "|" "/" "."))
           (cond
             ((= n 1) (string-append "\bigl"  s))
             ((= n 2) (string-append "\Bigl"  s))
             ((= n 3) (string-append "\biggl" s))
             ((= n 4) (string-append "\Biggl" s))
             (else (string-append "left" s))
           )
         )
         ((== s "||") "\\|")
         ((== s "\\") "\\backslash")
         (else (string-append "\\" s))
       )
      ))
   )
)

; Same thing, with left -> right.
(define (tmtex-right l)
   (let (
         (s (car l))
         (n (if (> (length l) 1) (string->number (cadr l)) 0))
        )
     (list (string->symbol
       (cond
         ((nstring? (car l)) "right.")
         ((in? s '("(" ")" "[" "]" "{" "}" "|" "/" "."))
           (cond
             ((= n 1) (string-append "\bigr"  s))
             ((= n 2) (string-append "\Bigr"  s))
             ((= n 3) (string-append "\biggr" s))
             ((= n 4) (string-append "\Biggr" s))
             (else (string-append "right" s))
           )
         )
         ((== s "||") "\\|")
         ((== s "\\") "\\backslash")
         (else (string-append "\\" s))
       )
      ))
   )
)

As a result, the function tmtex-large-decode is used only by
tmtex-mid now.

I would also like to modify the function texout-eqn in
texout.scm to output \begin{equation*} and \end{equation*}
instead of \[ and \], but only if the amsmath package is
loaded.  But I don't know how to test for that condition.

					Kostas
Permalink | Reply | 1 comment |
headers
David Allouche | 13 Jun 2008 00:02

Re: Hlink and pdf or ps

On Mon, Jun 9, 2008 at 6:26 PM, apostolos1975
<apostolos.georgakis <at> gmail.com> wrote:
>
> Hi all,
>
> I am trying to export a pdf file that contains for example:
>
> <hlink|cnn|http://www.cnn.com>
>
> the result is plain text (the word cnn) not the link the I want it to be. If
> I export to html everything is ok but not in pdf or ps. I have search alot
> but couldnt find an answer.
>
> Any suggestion? Thanks in advance

TeXmacs cannot do it. The current PDF export is too dumb to make
hyperlinks. Fixing it is non-trivial.
Permalink | Reply | 0 comments |

Gmane