dirk.hunniger at googlemail
Dec 8, 2013, 12:30 PM
Post #29 of 35
I saw you started to work on an LaTeX Export yourself. I needed more
than 3 year for mine. So I want you to be aware that it might take you a
long time to come up with something that really works. I also want to
offer you to share all my experience with you if you decide to do it
yourself, since it might significantly speed up your develpment process.
Unfortunatly I am currently neither unimployed nor a student anymore and
can not esaly get out of my current full time position at university. So
I do not have much time actully help you. My project is actually also
using xelatex. The problem is that it is using freeserif by default and
you have to manully enable megafont to get full 16 Bit Unicode support.
Still this does not solve the problem that some codepoints in unicode
stand for more than one character and you have to take into account
external information to guess the character to print.
On 26.11.2013 16:01, C. Scott Ananian wrote:
> The new PDF rendering pipeline does indeed use XeLaTeX. I haven't
> used it to typeset non-latin scripts since a summer I spent at SIL in
> 1996 (and that might have been Omega, not XeLaTeX), so if you wanted
> to pitch in and help out I'd greatly appreciate it. To start with,
> short example LaTeX articles typeset in your script would probably
> help me ensure I've got all the prologue bits and packages right.
> On Mon, Nov 25, 2013 at 10:49 PM, Santhosh Thottingal
> <santhosh.thottingal [at] gmail> wrote:
>> To support complex
>> scripts<https://en.wikipedia.org/wiki/Complex_text_layout> we
>> need to use a tex system that can support Unicode and complex script
>> rendering system. Xetex <https://en.wikipedia.org/wiki/XeTeX> works very
>> well with these scripts.I tried the MediaWiki to Latex converter with
>> Malayalam script, and the result is buggy.
>> Wikitech-l mailing list
>> Wikitech-l [at] lists
Wikitech-l mailing list
Wikitech-l [at] lists