new beta

Hans Hagen

17 Feb 2009 17 Feb '09

1:29 p.m.

Hi, There is a new beta: a few additions to math as well as a prelude to new cjk support, now to be triggered explicitly (since the methods differ too much we cannot share them) \setscript[hangul] \setscript[hanzi] % arthur, is this the right name? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Show replies by date

Arthur Reutenauer

17 Feb 17 Feb

1:41 p.m.

...

\setscript[hanzi] % arthur, is this the right name?

That's indeed the Pinyin transcription of the word for "Chinese character", even if it's not widely used in English. The OpenType script tag, hani, is short for "Han Ideograph". Arthur

Dohyun Kim

7:05 p.m.

2009/2/18 Hans Hagen :

...

Hi,

There is a new beta: a few additions to math as well as a prelude to new cjk support, now to be triggered explicitly (since the methods differ too much we cannot share them)

\setscript[hangul]

Now the Korean typesetting has become almost perfect. Thanks a lot, Hans. I really appreciate it. We have three more things to do, however. 1. inter_char_stretch_factor = 2.00 seems to be too large value. I do not think that even Chinese or Japanese would allow that big value. I suggest 0.50 instead. Mr Wang, how do you think about that? 2. Upon tracing output, I get : ..............\*unbatang12ptrmtfrm* 居 ..............\penalty 10000 ..............\*unbatang12ptrmtfrm* ) ..............\penalty 10000 %% this should be deleted. ..............\glue 0.0 plus 6.0 ..............\*unbatang12ptrmtfrm* 하 \panalty10000 after closing parenthesis should be deleted, so that line-breaking can occur at this point. 3. Line-breaking rule for medieval Korean is a little imperfect. When input string is "가나", all from Hangul Jamo area, I get : ..............\*unbatang12ptrmtfrm* % U+1100 ..............\*unbatang12ptrmtfrm* % U+1161 %% \penalty50 should be inserted here ..............\*unbatang12ptrmtfrm* % U+1102 ..............\*unbatang12ptrmtfrm* % U+1161 As I said in a private email with Hans, ^(OP | LC) allowbreak (LC) is another typesetting rule for Korean, where OP stands for Openings and LC for Leading Consonants (U+1100 .. U+115F). In the above output, as U+1161 is non-LC character, line-breaking should be allowed between U+1161 and U+1102. Dohyun Kim

Yanrui Li

18 Feb 18 Feb

11:36 p.m.

2009/2/18 Dohyun Kim :

...

We have three more things to do, however.

1. inter_char_stretch_factor = 2.00 seems to be too large value. I do not think that even Chinese or Japanese would allow that big value. I suggest 0.50 instead. Mr Wang, how do you think about that?

I modified these value as follows: fonts.analyzers.methods.hang_data = { inter_char_stretch_factor = 0.50, inter_char_half_factor = 0.25, inter_char_half_shrink_factor = 0.25, } However I had to tolerate the problem of Chinese puncuations appeared on the right side of pages which often affect the aesthetic feel of typesetting. -- Best wishes, Li Yanrui * Gentoo Linux (~x86) * LuaTeX (snapshot-0.31.3-2008122919) * ConTeXt Minimals (2009.01.18 14:39)

Hans Hagen

19 Feb 19 Feb

1:18 p.m.

Dohyun Kim wrote:

...

2009/2/18 Hans Hagen :

...
Hi,

There is a new beta: a few additions to math as well as a prelude to new cjk support, now to be triggered explicitly (since the methods differ too much we cannot share them)

\setscript[hangul]

Now the Korean typesetting has become almost perfect. Thanks a lot, Hans. I really appreciate it.

We have three more things to do, however.

1. inter_char_stretch_factor = 2.00 seems to be too large value. I do not think that even Chinese or Japanese would allow that big value. I suggest 0.50 instead. Mr Wang, how do you think about that?

...

2. Upon tracing output, I get :

..............\*unbatang12ptrmtfrm* 居 ..............\penalty 10000 ..............\*unbatang12ptrmtfrm* ) ..............\penalty 10000 %% this should be deleted. ..............\glue 0.0 plus 6.0 ..............\*unbatang12ptrmtfrm* 하

\panalty10000 after closing parenthesis should be deleted, so that line-breaking can occur at this point.

so ... ..._close = { jamo_initial = stretch_break, korean = stretch_break, chinese = stretch_break, half_width_open = stretch_break, half_width_close = nobreak_stretch, full_width_open = stretch_break, full_width_close = nobreak_stretch, hyphen = nobreak_stretch, non_starter = nobreak_stretch, other = stretch_break, },

...

3. Line-breaking rule for medieval Korean is a little imperfect. When input string is "가나", all from Hangul Jamo area, I get :

..............\*unbatang12ptrmtfrm* % U+1100 ..............\*unbatang12ptrmtfrm* % U+1161 %% \penalty50 should be inserted here ..............\*unbatang12ptrmtfrm* % U+1102 ..............\*unbatang12ptrmtfrm* % U+1161

As I said in a private email with Hans, ^(OP | LC) allowbreak (LC) is another typesetting rule for Korean, where OP stands for Openings and LC for Leading Consonants (U+1100 .. U+115F). In the above output, as U+1161 is non-LC character, line-breaking should be allowed between U+1161 and U+1102.

ok, but that's the chinese (hanzi) rule set, i added it it, but the chinese ruleset probably needs some more checking btw, there is not much halfwidth correction code enabled yet but first we need to decide on a reference font for chinese (or korean we have the unbatang) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Dohyun Kim

18 Feb 18 Feb

6:49 p.m.

2009/2/18 Hans Hagen :

...

Hi,

There is a new beta: a few additions to math as well as a prelude to new cjk support, now to be triggered explicitly (since the methods differ too much we cannot share them)

\setscript[hangul]

\setscript[hanzi] % arthur, is this the right name?

I have tested Chinese translation of Universal Declaration of Human Rights available at http://www.un.org/chinese/hr/issue/udhr.htm . 1. ........................\**thedefinedfont** 认 ........................\glue 0.0 plus 20.0 %% line break should not occur ........................\**thedefinedfont** ， % U+FF0C ........................\glue 0.0 plus 20.0 ........................\**thedefinedfont** 乃 Line break is prohibited before U+FF0C (fullwidth comma) but current beta inserts glue. This should be corrected. The same for U+FF1B (fullwidth semicolon). 2. ........................\**thedefinedfont** 由 ........................\penalty 10000 ........................\glue 0.0 plus 20.0 ........................\**thedefinedfont** 、 % U+3001 ........................\penalty 10000 %% this should be deleted ........................\glue 0.0 minus 5.0 ........................\glue 0.0 plus 20.0 ........................\**thedefinedfont** 正 Line break is allowed after U+3001 (ideographic comma), so \penalty10000 after U+3001 should not be inserted. The same for U+3002 (ideographic full stop). 3. I don't know much about Chinese typesetting, but IMO it would be better if these full width CJK punctuations is forced to half width and 0.5em glue is inserted after those characters. Dohyun Kim

Yue Wang

9:24 p.m.

2009/2/19 Dohyun Kim

...

2009/2/18 Hans Hagen :

...
Hi,

There is a new beta: a few additions to math as well as a prelude to new cjk support, now to be triggered explicitly (since the methods differ too much we cannot share them)

\setscript[hangul]

\setscript[hanzi] % arthur, is this the right name?

I have tested Chinese translation of Universal Declaration of Human Rights available at http://www.un.org/chinese/hr/issue/udhr.htm .

1. ........................\**thedefinedfont** 认 ........................\glue 0.0 plus 20.0 %% line break should not occur ........................\**thedefinedfont** ， % U+FF0C ........................\glue 0.0 plus 20.0 ........................\**thedefinedfont** 乃

Line break is prohibited before U+FF0C (fullwidth comma) but current beta inserts glue. This should be corrected. The same for U+FF1B (fullwidth semicolon).

right

...

2. ........................\**thedefinedfont** 由 ........................\penalty 10000 ........................\glue 0.0 plus 20.0 ........................\**thedefinedfont** 、 % U+3001 ........................\penalty 10000 %% this should be deleted ........................\glue 0.0 minus 5.0 ........................\glue 0.0 plus 20.0 ........................\**thedefinedfont** 正

Line break is allowed after U+3001 (ideographic comma), so \penalty10000 after U+3001 should not be inserted.

umm... maybe... I am not sure...

...

The same for U+3002 (ideographic full stop).

right

...

3. I don't know much about Chinese typesetting, but IMO it would be better if these full width CJK punctuations is forced to half width and 0.5em glue is inserted after those characters.

We can use the bounding box information of these punctuations.

...

Dohyun Kim

___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net

___________________________________________________________________________________

Hans Hagen

19 Feb 19 Feb

3:04 a.m.

Dohyun Kim wrote:

...

I have tested Chinese translation of Universal Declaration of Human Rights available at http://www.un.org/chinese/hr/issue/udhr.htm .

can you send me a zip with your test file so that we test the same? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Dohyun Kim

4:55 a.m.

2009/2/19 Hans Hagen :

...

Dohyun Kim wrote:

...
I have tested Chinese translation of Universal Declaration of Human Rights available at http://www.un.org/chinese/hr/issue/udhr.htm .

can you send me a zip with your test file so that we test the same?

Attached. Nothing special; just copy and pasted from the web site. On the other hand, as Yanrui's sample seems to be much better than mine, I made an illustration of Japanese typesetting rule on his sample: http://people.ktug.or.kr/~nomos/mine/japanesetypesetting.png . I guess that Chinese typesetting practice is not much different from this one. Dohyun Kim

Yue Wang

6:36 a.m.

On Thu, Feb 19, 2009 at 7:55 PM, Dohyun Kim wrote:

...

2009/2/19 Hans Hagen :

...
Dohyun Kim wrote:

...
I have tested Chinese translation of Universal Declaration of Human Rights available at http://www.un.org/chinese/hr/issue/udhr.htm .

can you send me a zip with your test file so that we test the same?

Attached. Nothing special; just copy and pasted from the web site.

On the other hand, as Yanrui's sample seems to be much better than mine, I made an illustration of Japanese typesetting rule on his sample: http://people.ktug.or.kr/~nomos/mine/japanesetypesetting.png . I guess that Chinese typesetting practice is not much different from this one.

Maybe it is different (I have no idea about Japanese typesetting, I can only speak Chinese, English, and Korean). - There are no "halfwidth punctuation" in most Chinese fonts. All the glyphs in those fonts are of same width. Only a small portion of Chinese fonts (like Adobe's OpenType fonts) contain these glyphs in certain features. - halfwidth glyph+0.5em minus0.5em ( = 1em) is not right, the punctuation should be compressed. some combinations like ：" should also be compressed. Yue Wang

...

Dohyun Kim

___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Yue Wang

6:59 a.m.

Hi, all.

...

Maybe it is different (I have no idea about Japanese typesetting, I can only speak Chinese, English, and Korean). - There are no "halfwidth punctuation" in most Chinese fonts. All the glyphs in those fonts are of same width. Only a small portion of Chinese fonts (like Adobe's OpenType fonts) contain these glyphs in certain features. - halfwidth glyph+0.5em minus0.5em ( = 1em) is not right, the punctuation should be compressed. some combinations like ：" should also be compressed.

Sorry for the noise... I just want to say that Li Yanrui's example does not show excellent Chinese typesetting. Maybe there is something wrong here... Yue Wang

Wolfgang Schuster

7:37 a.m.

Am 19.02.2009 um 14:59 schrieb Yue Wang:

...

...
Maybe it is different (I have no idea about Japanese typesetting, I can only speak Chinese, English, and Korean). - There are no "halfwidth punctuation" in most Chinese fonts. All the glyphs in those fonts are of same width. Only a small portion of Chinese fonts (like Adobe's OpenType fonts) contain these glyphs in certain features. - halfwidth glyph+0.5em minus0.5em ( = 1em) is not right, the punctuation should be compressed. some combinations like ：" should also be compressed.

Sorry for the noise... I just want to say that Li Yanrui's example does not show excellent Chinese typesetting. Maybe there is something wrong here...

The spacing between the punctuation is wrong and the comma shouldn't be at the begin of the line. I made a short file with a few examples a while ago. Wolfgang

Wolfgang Schuster

7:28 a.m.

Am 19.02.2009 um 14:36 schrieb Yue Wang:

...

...
On the other hand, as Yanrui's sample seems to be much better than mine, I made an illustration of Japanese typesetting rule on his sample: http://people.ktug.or.kr/~nomos/mine/japanesetypesetting.png . I guess that Chinese typesetting practice is not much different from this one.

Maybe it is different (I have no idea about Japanese typesetting, I can only speak Chinese, English, and Korean). - There are no "halfwidth punctuation" in most Chinese fonts. All the glyphs in those fonts are of same width. Only a small portion of Chinese fonts (like Adobe's OpenType fonts) contain these glyphs in certain features. - halfwidth glyph+0.5em minus0.5em ( = 1em) is not right, the punctuation should be compressed. some combinations like ：" should also be compressed.

What method do you want to use. 1. Make a punctuation half width and insert space between them, e.g. 組版\hbox to .5em{」\hss}\hbox to .5em{。\hss} \hskip .5em\hbox to .5em{\hss「}原則 2. Let the punctuation full width and kern char combinations, e.g. 組版」\kern.5em。\kern.5em「原則 Wolfgang

Yue Wang

9:13 a.m.

On Thu, Feb 19, 2009 at 10:28 PM, Wolfgang Schuster wrote:

...

What method do you want to use.

1. Make a punctuation half width and insert space between them, e.g. 組版\hbox to .5em{」\hss}\hbox to .5em{。\hss}\hskip .5em\hbox to .5em{\hss「}原則

2. Let the punctuation full width and kern char combinations, e.g. 組版」\kern.5em。\kern.5em「原則

neither. the position of the bounding box of a certain punctuation glyph is highly font-dependent. if we use the half/full width and set all the parameters constant, we will get ugly result when the font is changed. It is easy to compare sim*.ttf and find that the punctuation glyph positions in the metrics boxes of different fotns vary significantly. Moreover, some glyphs in the font takes more than half-width. You can open simli.ttf (distributed in windows xp), and find glyph quotedblright 8821 (RIGHT DOUBLE QUOTATION MARK), the max_y = 130 while a em=256. And these are not rare cases. In the same font, different punctuation have very different bounding box position in the font metrics too. for quotedblright 8821 (RIGHT DOUBLE QUOTATION MARK) in simli.ttf, max_y=130, while for uni3002 at 12290 (IDEOGRAPHIC FULL STOP) in simli.ttf, max_y=82. it is not fair to set equal width for them. So we should not cut a glyph into half and take the left part for typesetting. Due to some reasons dates back from early days of computer typeface design (at the old days, we have no idea about proportional width, all the glyphs are set to square [for CJK]. Operating systems or Document processing systems all use square or half of a square to position and render glyphs), CJK fonts are usually designed with equal width, even for punctuations. This is really bad: while typesetting, they do not take up same space. So my idea is to convert the punctuation glyphs' bounding box information into TFM width parameters (leave a little space at left and right), so the CJK typesetting problem is reduced to Latin typesetting problems. We can also position the glyph at the begin or end of the line close to the margin (or even calculate the exact space for margin kerning). btw, we prefer typesetting Chinese document like this: http://jjgod.org/docs/random/yt.pdf This is a document produced using XeTeX and xeCJK package typeset by Jiang Jiang. All the glue/penalty rules are carefully optimized by the people from local TeX community, although not using the bounding box information (impossible to get from XeTeX). Yue Wang

luigi scarso

9:47 a.m.

...

btw, we prefer typesetting Chinese document like this:

http://jjgod.org/docs/random/yt.pdf

forgive me for intrusion $>pdfinfo yt.pdf Creator: LaTeX with hyperref package Producer: xdvipdfmx (0.7.3) CreationDate: Sat Dec 27 16:17:05 2008 Tagged: no Pages: 533 Encrypted: no Page size: 498.9 x 708.66 pts File size: 2966285 bytes Optimized: no PDF version: 1.4 $>pdffonts yt.pdf name type emb sub uni object ID ------------------------------------ ----------------- --- --- --- --------- TYNLGQ+FZKTK--GBK1-0 CID TrueType yes yes yes 8 0 GBLMNF+SabonLTStd-Bold-Identity-H CID Type 0C yes yes yes 15 0 XJQTVQ+SabonLTStd-Roman-Identity-H CID Type 0C yes yes yes 32 0 Error: Unknown character collection 'Adobe-GB1' ADRNAX+AdobeFangsongStd-Regular-Identity-H CID Type 0C yes yes no 318 0 Error: Unknown character collection 'Adobe-GB1' Why ? -- luigi

Yanrui Li

10:03 a.m.

2009/2/20 luigi scarso :

...

...
btw, we prefer typesetting Chinese document like this:

http://jjgod.org/docs/random/yt.pdf

forgive me for intrusion

$>pdfinfo yt.pdf Creator: LaTeX with hyperref package Producer: xdvipdfmx (0.7.3) CreationDate: Sat Dec 27 16:17:05 2008 Tagged: no Pages: 533 Encrypted: no Page size: 498.9 x 708.66 pts File size: 2966285 bytes Optimized: no PDF version: 1.4

$>pdffonts yt.pdf name type emb sub uni object ID ------------------------------------ ----------------- --- --- --- --------- TYNLGQ+FZKTK--GBK1-0 CID TrueType yes yes yes 8 0 GBLMNF+SabonLTStd-Bold-Identity-H CID Type 0C yes yes yes 15 0 XJQTVQ+SabonLTStd-Roman-Identity-H CID Type 0C yes yes yes 32 0 Error: Unknown character collection 'Adobe-GB1' ADRNAX+AdobeFangsongStd-Regular-Identity-H CID Type 0C yes yes no 318 0

Error: Unknown character collection 'Adobe-GB1' Why ?

Hi, If you use poppler as your pdf render engine, you can try to install the package "poppler-data" which are data files for poppler to support uncommon encodings without xpdfrc.

...

-- luigi ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

-- Best wishes, Li Yanrui * Gentoo Linux (~x86) * LuaTeX (snapshot-0.33.1-2009021608, build 1866) * ConTeXt Minimals (2009.02.17 18:50)

luigi scarso

2:59 p.m.

On Thu, Feb 19, 2009 at 6:03 PM, Yanrui Li wrote:

...

2009/2/20 luigi scarso :

...
...
btw, we prefer typesetting Chinese document like this:

http://jjgod.org/docs/random/yt.pdf

forgive me for intrusion

$>pdfinfo yt.pdf Creator: LaTeX with hyperref package Producer: xdvipdfmx (0.7.3) CreationDate: Sat Dec 27 16:17:05 2008 Tagged: no Pages: 533 Encrypted: no Page size: 498.9 x 708.66 pts File size: 2966285 bytes Optimized: no PDF version: 1.4

$>pdffonts yt.pdf name type emb sub uni object ID ------------------------------------ ----------------- --- --- --- --------- TYNLGQ+FZKTK--GBK1-0 CID TrueType yes yes yes 8 0 GBLMNF+SabonLTStd-Bold-Identity-H CID Type 0C yes yes yes 15 0 XJQTVQ+SabonLTStd-Roman-Identity-H CID Type 0C yes yes yes 32 0 Error: Unknown character collection 'Adobe-GB1' ADRNAX+AdobeFangsongStd-Regular-Identity-H CID Type 0C yes yes no 318 0

Error: Unknown character collection 'Adobe-GB1' Why ? Because I supposed that all Language Support Packages were installed (cfr http://gd.tuwien.ac.at/publishing/xpdf/) But this was not true . Sorry for the noise.

Hi,

If you use poppler as your pdf render engine, you can try to install the package "poppler-data" which are data files for poppler to support uncommon encodings without xpdfrc. ok thank you .

-- luigi

Hans Hagen

1:30 p.m.

Yue Wang wrote:

...

On Thu, Feb 19, 2009 at 7:55 PM, Dohyun Kim wrote:

...
2009/2/19 Hans Hagen :

...
Dohyun Kim wrote:

...
I have tested Chinese translation of Universal Declaration of Human Rights available at http://www.un.org/chinese/hr/issue/udhr.htm . can you send me a zip with your test file so that we test the same?

Attached. Nothing special; just copy and pasted from the web site.

On the other hand, as Yanrui's sample seems to be much better than mine, I made an illustration of Japanese typesetting rule on his sample: http://people.ktug.or.kr/~nomos/mine/japanesetypesetting.png . I guess that Chinese typesetting practice is not much different from this one.

Maybe it is different (I have no idea about Japanese typesetting, I can only speak Chinese, English, and Korean). - There are no "halfwidth punctuation" in most Chinese fonts. All the glyphs in those fonts are of same width. Only a small portion of Chinese fonts (like Adobe's OpenType fonts) contain these glyphs in certain features. - halfwidth glyph+0.5em minus0.5em ( = 1em) is not right, the punctuation should be compressed. some combinations like ：" should also be compressed.

The problem is in the 'ascii' opening/closing and punctiation. In Korean proper latin fonts are mixed with korean (fixed width) fonts, whil ein chinese (i suppose) the chinese punctuation is to be used. It's no problem to compensate for hw there. Hoewever, what to do with the non-chinese punctionation. Ok, we can mess around with the width but isn't it better then to use the right chinese characters in the first place? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Yanrui Li

2:38 a.m.

2009/2/18 Hans Hagen :

...

Hi,

There is a new beta: a few additions to math as well as a prelude to new cjk support, now to be triggered explicitly (since the methods differ too much we cannot share them)

\setscript[hangul]

\setscript[hanzi] % arthur, is this the right name?

Hi, I found that we can't copy the texts from pdf generated by new beta for Chinese. The attachment is my test files. -- Best wishes, Li Yanrui * Gentoo Linux (~x86) * LuaTeX (snapshot-0.33.1-2009021608, build 1866) * ConTeXt Minimals (2009.02.17 18:50)

Hans Hagen

2:45 a.m.

Yanrui Li wrote:

...

2009/2/18 Hans Hagen :

...
Hi,

There is a new beta: a few additions to math as well as a prelude to new cjk support, now to be triggered explicitly (since the methods differ too much we cannot share them)

\setscript[hangul]

\setscript[hanzi] % arthur, is this the right name?

Hi,

I found that we can't copy the texts from pdf generated by new beta for Chinese. The attachment is my test files.

you need the latest luatex for that ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Taco Hoekwater

3:03 a.m.

Hans Hagen wrote:

...

you need the latest luatex for that

And a new luatex beta release is planned for tuesday. Best wishes, Taco

Alan BRASLAU

7 Mar 7 Mar

1:45 a.m.

...

I uploaded a new beta (mkiv)

ppchtex is broken using yesterday's beta.

Hans Hagen

5:29 a.m.

Alan BRASLAU wrote:

...

...
I uploaded a new beta (mkiv)

ppchtex is broken using yesterday's beta.

examples please ... -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Alan BRASLAU

8 Mar 8 Mar

12:11 a.m.

Anything :) (for example: \usemodule[chemic] \starttext \startchemical[size=small,scale=200,width=fit,frame=off] \chemical[SIX,B,C,R,RZ][R,R,R,R,R,R] \stopchemical \stoptext see attached result.) On Saturday 07 March 2009 13:29:23 Hans Hagen wrote:

...

Alan BRASLAU wrote:

...
...
I uploaded a new beta (mkiv)

ppchtex is broken using yesterday's beta.

examples please ...

Hans Hagen

10:27 a.m.

Alan BRASLAU wrote:

...

Anything :)

(for example:

\usemodule[chemic]

\starttext \startchemical[size=small,scale=200,width=fit,frame=off] \chemical[SIX,B,C,R,RZ][R,R,R,R,R,R] \stopchemical \stoptext

see attached result.)

ok, typo in the mp/tex bits ... (side effect to otf tracing using mp) i fixed it in the beta but since i'm working on some code cleanup .. can you test asap if you can make a format (i.e. if all files are in the zip) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

5609

Age (days ago)

5628

Last active (days ago)

List overview

Download

24 comments

9 participants

participants (9)

Alan BRASLAU
Arthur Reutenauer
Dohyun Kim
Hans Hagen
luigi scarso
Taco Hoekwater
Wolfgang Schuster
Yanrui Li
Yue Wang

new beta

tags

participants (9)