Re: [NTG-context] Chinese

2005-12-09 Thread Tobias Burnus

Hi,

Xiao Jianfeng wrote:

Maybe it is beacuse of the encoding of your .tex  file.
The encoding of my tex source file is cp936 and I edit with gvim.
ConTeXt compiles OK when processing Chinese. I din't use 
\enableregime[utf] or \language[cn] to typeset Chinese.
Ok this works. Another possibility is to use the script by Lutz (see 
link in the wiki) which converts UTF8 to gbk.
However, both solutions have the drawback that e.g. ä does not get 
typset (there is no ä in gbk).


What would be needed to get UTF-8 input running with Chinese?

Tobias

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Duncan Hothersall
Tobias Burnus asks:

 What would be needed to get UTF-8 input running with Chinese?

If there is a recipe, I would like to help cook it. Getting UTF-8 input
running with Chinese would be a godsend to me too.

Duncan
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] Re: mfonts.tex from manuals

2005-12-09 Thread Mojca Miklavec
piskala upendran wrote:
 hi, Mojca

 The complain about the fonts is 8t encoding. use 8r
 encoding. it should work ok.

 I got the palatino font using 8r encoding using the
 following.

 \usetypescript [adobekb][\defaultencoding]
 \usetypescript [palatino][\defaultencoding]
 \setupbodyfont[palatino,10pt]

 it should compile ok.

Thank you very much. I replaced
\usetypescriptfile[type-buy]
with
\usetypescript [adobekb][\defaultencoding]
which finally worked.

Installing cont-fnt as Hans suggested didn't have any influence at all.


However, now some really strange bug(?) appeared.
\type{\whatevercommand} doesn't work inside \starttabulate ...
\stoptabulate. This is only true for MikTeX, everywhere else it works
OK. \starttabulate and \type{\whatevercommand} both work when they are
used separately, but fail when \type comes inside \starttabulate.

It may be that MikTeX is a bit old (27.10.), but there is no newer
version available yet, so I hope that the problem will go away with
the next version.

Mojca


! Missing $ inserted.
inserted text
$
to be read again
   \atop
\tabulatecontent -\NC \type {\atop
} \NC \NR
\fulltabulatecontent ...dcontent \tabulatecontent
  \tabulatetailcontent \remo...

\processtabulate ...sa \crcr \fulltabulatecontent
  \crcr }}\ifnum \nofautotab...
l.4 \stoptabulate

?
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Xiao Jianfeng

Hi,

Tobias Burnus wrote:


Hi,

Xiao Jianfeng wrote:


Maybe it is beacuse of the encoding of your .tex  file.
The encoding of my tex source file is cp936 and I edit with gvim.
ConTeXt compiles OK when processing Chinese. I din't use 
\enableregime[utf] or \language[cn] to typeset Chinese.


Ok this works. Another possibility is to use the script by Lutz (see 
link in the wiki) which converts UTF8 to gbk.
However, both solutions have the drawback that e.g. ä does not get 
typset (there is no ä in gbk).


What would be needed to get UTF-8 input running with Chinese?

Tobias

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

If you use vim to edit your tex file, maybe you can try set 
encoding=utf8, then save and compile.

As far as I know, GBK is compatible with unicode.

I'm not sure if it works or not. I don't konw too much about encoding.

Regards,
xiaojf
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Tobias Burnus

Hi,

Xiao Jianfeng wrote:

What would be needed to get UTF-8 input running with Chinese?
If you use vim to edit your tex file, maybe you can try set 
encoding=utf8, then save and compile.

As far as I know, GBK is compatible with unicode.

No, that does not work - that is the reason I started this mail thread.
You get the wrong characters and you may get some TeX errors.
(And that is the reason Lutz wrote a UTF-8 to GBK converted.)

Tobias
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] modes in newtexexec

2005-12-09 Thread Johan Sandblom
Hello.

Doing

texmfstart texexec

now appears to call newtexexec. However, newtexexec does not seem to
handle --mode at all. Is it coming? Should I set it up so I can call
texexec directly in order to use modes?

Regards, Johan
--
Johan Sandblom  N8, MRC, Karolinska sjh
t +46851776108  17176 Stockholm
m +46735521477  Sweden
What is wanted is not the will to believe, but the
will to find out, which is the exact opposite
- Bertrand Russell
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Xiao Jianfeng

Tobias Burnus wrote:


Hi,

Xiao Jianfeng wrote:


What would be needed to get UTF-8 input running with Chinese?


If you use vim to edit your tex file, maybe you can try set 
encoding=utf8, then save and compile.

As far as I know, GBK is compatible with unicode.


No, that does not work - that is the reason I started this mail thread.
You get the wrong characters and you may get some TeX errors.
(And that is the reason Lutz wrote a UTF-8 to GBK converted.)

Tobias
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


So, maybe the problem has something to do with you input method.
How do you input Chinese in your system ?

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Xiao Jianfeng

Tobias Burnus wrote:


Hi,

Xiao Jianfeng wrote:


What would be needed to get UTF-8 input running with Chinese?


If you use vim to edit your tex file, maybe you can try set 
encoding=utf8, then save and compile.

As far as I know, GBK is compatible with unicode.


No, that does not work - that is the reason I started this mail thread.
You get the wrong characters and you may get some TeX errors.
(And that is the reason Lutz wrote a UTF-8 to GBK converted.)

Tobias
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


What is the value of your environment variables about LC_CTYPE and LANG ?

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Adam Lindsay

Tobias Burnus wrote:

Hi,

Xiao Jianfeng wrote:


What would be needed to get UTF-8 input running with Chinese?


If you use vim to edit your tex file, maybe you can try set 
encoding=utf8, then save and compile.

As far as I know, GBK is compatible with unicode.


No, that does not work - that is the reason I started this mail thread.
You get the wrong characters and you may get some TeX errors.
(And that is the reason Lutz wrote a UTF-8 to GBK converted.)


Hmm, I suspect that some remix between my old (deprecated) Libertine in 
ConTeXt recipe and the ttf2tfm automatic unicode splitting would have 
some positive effects.


(I would discourage using that recipe for alphabetic (incl Roman) 
Unicode fonts because it blows away any kerning that would happen 
between unicode blocks. Is there less kerning among CJK fonts? I would 
expect so.)


Thinking aloud, you'd probably want to include some language-switching 
commands, to mediate between the calling of unicode fonts for un-named 
CJK glyphs (just raw conversion from Unicode to font switch + glyph 
number) to named roman (and other alphabetic) glyphs (conversion from 
UTF-8 to named glyphs to font+glyph, which retains kerning where it can).


I know it's sketchy and vague, but have a look inside font-uni. It's not 
the most complicated file in the distro.


adam
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED]
 Lancaster University, InfoLab21+44(0)1524/510.514
 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Tobias Burnus

Hi,

Xiao Jianfeng wrote:

What is the value of your environment variables about LC_CTYPE and LANG ?

Well, I use SCIM to input the characters and my locale is de_DE.UTF-8.
As the input works everywhere (OpenOffice, vim in Xterm, gvim etc.) I'm 
positiv that the problem is the lacking support of UTF-8 encoding of 
Chinese in ConTeXt and that this is not a problem of the encoding being 
wrong.


Looking at the cp936 to Unicode table 
(http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP936.TXT) 
one sees that they are not the same.


A rough big5 to Unicode table can be found at 
http://www.unicode.org/Public/MAPPINGS/OBSOLETE/EASTASIA/OTHER/BIG5.TXT



Tobias
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Richard Gabriel




Hi guys,I can confirm that the UTF-8 input doesn't work for me too. If I convert the file info GBK (CP936), it works fine [I suggest to use the 'iconv' utility for the conversion :-)].I tested the UTF-8 output the followin ways:1) \enableregime[utf]\usemodule[chinese]Processing a file with this setup ends with an error:--- cut ---kpathsea: Running mktextfm gbsong80mktextfm: Could not map typeface abbreviation bs for gbsong80.mktextfm: Need to update c:/WinApp/TeXLive/texmf-dist/fonts/map/fontname/special.map?mktextfm: Running mf "\mode:=ljfour; mag:=1; nonstopmode; input gbsong80"This is METAFONT, Version 2.71828 (Web2c 7.5.5)kpathsea: Running mktexmf gbsong80mktexmf: empty or non-existent rootfile!! I can't find file `gbsong80'.* ...ljfour; mag:=1; nonstopmode; input gbsong80Please type another input file name! Emergency stop.* ...ljfour; mag:=1; nonstopmode; input gbsong80Transcript written on mfput.log.mktextfm: warning: can't open log file gbsong80.log.mktextfm: `mf "\mode:=ljfour; mag:=1; nonstopmode; input gbsong80"' failed.kpathsea: Appending font creation commands to missfont.log.! Font \unicodefont=gbsong80 at 24.88806pt not loadable: Metric (TFM) file notfound.--- cut ---
I cannot figure out why it wants "gbsong80" when the encoding vector set starts from the 0x81 offset. Maybe some error in the UTF mapping?2)\usemodule[chinese]
\enableregime[utf]
No error, but not output!The PDF contains only black squares instead of glyphs.The log shows that no fonts were used at all!-RichardFrom: Xiao Jianfeng [mailto:[EMAIL PROTECTED]To: mailing list for ConTeXt users [mailto:[EMAIL PROTECTED]Sent: Fri, 09 Dec 2005 15:24:22 +0100Subject: Re: [NTG-context] ChineseTobias Burnus wrote: Hi, Xiao Jianfeng wrote: What would be needed to get UTF-8 input running with Chinese? If you use vim to edit your tex file, maybe you can try "set  encoding=utf8", then save and compile. As far as I know, GBK is compatible with unicode. No, that does not work - that is the reason I started this mail thread. You get the wrong characters and you may get some TeX errors. (And that is the reason Lutz wrote a UTF-8 to GBK converted.) Tobias ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-contextWhat is the value of your environment variables about LC_CTYPE and LANG ?___ntg-context mailing listntg-context@ntg.nlhttp://www.ntg.nl/mailman/listinfo/ntg-context
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Chinese

2005-12-09 Thread Tobias Burnus

Hi,

Adam Lindsay wrote:

Is there less kerning among CJK fonts? I would expect so.
Classically any Chinese character has exactly the same width, which is 
the same as the height (square). Nowadays some are taller than wide. I'm 
quite certain that there is hardly any Chinese font with kerning as this 
would break the grid.


Thinking aloud, you'd probably want to include some language-switching 
commands, to mediate between the calling of unicode fonts for un-named 
CJK glyphs (just raw conversion from Unicode to font switch + glyph 
number) to named roman (and other alphabetic) glyphs (conversion from 
UTF-8 to named glyphs to font+glyph, which retains kerning where it can).
Well, I think one uses most of the time different fonts for Chinese and 
non-CJK texts as many Chinese fonts don't include that many roman 
letters (at least the ones quoted at 
http://wiki.contextgarden.net/Chinese miss the ß and ä).


Tobias

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] fonts

2005-12-09 Thread Henning Hraban Ramm

Am 2005-12-09 um 00:08 schrieb Adam Lindsay:

(or do you know a link of Apostrophe  Lab?).

I've found most of them on DAFont:
http://www.dafont.com/en/author.php?author=128


Ah, thank you!
Would be a real pity if they would've been lost.

BTW I just made a symbol set for HardTalk:
http://www.dafont.com/en/author.php?author=128page=5
I won't post it here (there may be Apuricans on this list)...


Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context