[NTG-context] persian interface broken?
Hi
I just noticed that making the persian formats (context --make cont-pe) fails
with:
! Undefined control sequence.
-\zwnj
argument تعریف
درونحاشیه
\do@sicom #1#2-\@EA \gdef \csname #2
\@EA \endcsname \@EA {\csname #1\endcsn...
l.5300 }
l.31 ...(\userinterfacetag,\userresponsestag)}
Log attached.
Is this known?
I don't really need it, just want to know if this is suppose to work with
recent context.
Adam
resolvers | resolving | configuration files already identified
resolvers | resolving | loading configuration file '/usr/share/texmf/web2c/texmfcnf.lua'
resolvers | resolving |
resolvers | resolving | locating list of 'home:texmf' (runtime)
resolvers | methods | resolver: method=locators, how=uri, scheme=file, argument=home:texmf
resolvers | files | file locator 'home:texmf' not found
resolvers | resolving | locating list of 'selfautoparent:texmf-project' (cached)
resolvers | methods | resolver: method=locators, how=uri, scheme=file, argument=selfautoparent:texmf-project
resolvers | files | file locator 'selfautoparent:texmf-project' not found
resolvers | resolving | locating list of 'selfautoparent:texmf-fonts' (cached)
resolvers | methods | resolver: method=locators, how=uri, scheme=file, argument=selfautoparent:texmf-fonts
resolvers | files | file locator 'selfautoparent:texmf-fonts' not found
resolvers | resolving | locating list of '/usr/local/share/texmf' (cached)
resolvers | methods | resolver: method=locators, how=uri, scheme=file, argument=/usr/local/share/texmf
resolvers | files | file locator '/usr/local/share/texmf' found as '/usr/local/share/texmf'
resolvers | resolving | locating list of '/usr/share/texmf' (runtime)
resolvers | methods | resolver: method=locators, how=uri, scheme=file, argument=/usr/share/texmf
resolvers | files | file locator '/usr/share/texmf' found as '/usr/share/texmf'
resolvers | resolving | locating list of 'selfautoparent:texmf-linux' (cached)
resolvers | methods | resolver: method=locators, how=uri, scheme=file, argument=selfautoparent:texmf-linux
resolvers | files | file locator 'selfautoparent:texmf-linux' not found
resolvers | resolving | locating list of '/usr/share/texmf-texlive' (runtime)
resolvers | methods | resolver: method=locators, how=uri, scheme=file, argument=/usr/share/texmf-texlive
resolvers | files | file locator '/usr/share/texmf-texlive' found as '/usr/share/texmf-texlive'
resolvers | resolving |
resolvers | methods | resolver: method=generators, how=uri, scheme=file, argument=/usr/local/share/texmf
resolvers | expansions | scanning path '/usr/local/share/texmf', branch '/usr/local/share/texmf'
resolvers | expansions | 1 files found on 0 directories with 1 uppercase remappings
resolvers | methods | resolver: method=generators, how=uri, scheme=file, argument=/usr/share/texmf
resolvers | expansions | scanning path '/usr/share/texmf', branch '/usr/share/texmf'
resolvers | expansions | 13935 files found on 781 directories with 389 uppercase remappings
resolvers | methods | resolver: method=generators, how=uri, scheme=file, argument=/usr/share/texmf-texlive
resolvers | expansions | scanning path '/usr/share/texmf-texlive', branch '/usr/share/texmf-texlive'
resolvers | expansions | 47167 files found on 4775 directories with 2792 uppercase remappings
resolvers | resolving |
resolvers | resolving | saving tree '/usr/local/share/texmf'
resolvers | caches | hashing tree /usr/local/share/texmf, hash 5044cbe2799fe389b078f26ff6b9ee8e
resolvers | caching | preparing 'files' for '/usr/local/share/texmf'
resolvers | caching | category 'files', cachename '/usr/local/share/texmf' saved in '/home/reviczky/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/trees/5044cbe2799fe389b078f26ff6b9ee8e.lua'
system | logs | lua: compiling /home/reviczky/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/trees/5044cbe2799fe389b078f26ff6b9ee8e.lua into /home/reviczky/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/trees/5044cbe2799fe389b078f26ff6b9ee8e.luc
resolvers | caching | 'files' compiled to '/home/reviczky/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/trees/5044cbe2799fe389b078f26ff6b9ee8e.luc'
resolvers | resolving | saving tree '/usr/share/texmf'
resolvers | caches | hashing tree /usr/share/texmf, hash 0638a6bb4aac17125bf8bd1aa29dc0c8
resolvers | caching | preparing 'files' for '/usr/share/texmf'
resolvers | caching | category 'files', cachename '/usr/share/texmf' saved in '/home/reviczky/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/trees/0638a6bb4aac17125bf8bd1aa29dc0c8.lua'
system | logs | lua: compiling
Re: [NTG-context] Persian interface
On Thu, Oct 23, 2008 at 6:31 AM, Mehdi Omidali [EMAIL PROTECTED] wrote: On 10/21/08, Hans Hagen [EMAIL PROTECTED] wrote: Mehdi Omidali wrote: Hi everyone, I want to be able to use persian interface in context. So I tried to create two files cont-pe.xml and cont-pe.tex for this purpose. Now my questions are: 1- Am I supposed to just create these two files and then run context --make cont-pe. 2- Can context accept these two files in UTF-8 encoding. you need to adapt mult-con and mult-com but at the same time we need to adapt mult-sys, so as an experiment if things work out ok, just play a bit with mult-con/com e.g. replace a few harmless commands in the english interface and see if things work ok for persian footnote: voetnoot footnote fussnote poznamkapodcarou notapdp notasubsol notepdp eventually persian can become the 8th entry footnote: voetnoot somethingpersian fussnote poznamkapodcarou notapdp notasubsol notepdp \somethingpersian then should give you a footnote (we never really tested it with utf8 input so far) (when i have time i will (for luatex) make this mechanism different i.e. just lua tables from which i then can generate the con/com files) Hi Hans and everybody, I did as you said and saw two things. 1- The good news: it is possible to assign another name (even persian) for an option name. For example the word packed which is used as an option in some commands like \setupitemize works well if you substitute it with anything. 2- The bad news: names of commands (I mean words that is used in the input file with a backslash in front of them like footnote or setupsomething) are not well behaved if we change them in mult.con.tex. I tried to change for example the word footnote with a persian word with more than one character and in the running time I got the error that that command is not defined. But I was able to redefine footnote with a just one (persian) character. You need characters with catcode 11 for the commands and most of the chars outside the ASCII range have catcode 12 which can be used only in commands with the length 1 like your footnote example. Here is a example how to use umlauts for the german interface: \catcode`ü=11 \startcommandsdutchenglish german czech italian romanian french definittete setuphead: stelkopinsetuphead stelleüberschriftein nastavnadpis impostatesta seteazatitlu regletete \stopcommands Wolfgang ___ 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 ___
Re: [NTG-context] Persian interface
Wolfgang Schuster wrote:
You need characters with catcode 11 for the commands and most of the
chars outside the ASCII range have catcode 12 which can be used only
in commands with the length 1 like your footnote example.
hm, maybe the catcode initialization takes place too late
Here is a example how to use umlauts for the german interface:
in the next beta this system is replaced by another one:
- mult-def.lua
this is a table that has all variables, constants, elements and commands
in a hash which then can be extended without the need to adapt the tex code
- mult-en, mult-de, mult-nl ...
these are generated by mtxrun --script interface --contect
- cont-en.xml cum suis
the derived ones are also generated by the previously mentioned command
- stripped down mult-ini.{mkii,mkiv}
the other two files (mult-con and mult-com) are no longer used
taco and i are currently checking the new 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
-
___
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
___
Re: [NTG-context] Persian interface
On 10/21/08, Hans Hagen [EMAIL PROTECTED] wrote: Mehdi Omidali wrote: Hi everyone, I want to be able to use persian interface in context. So I tried to create two files cont-pe.xml and cont-pe.tex for this purpose. Now my questions are: 1- Am I supposed to just create these two files and then run context --make cont-pe. 2- Can context accept these two files in UTF-8 encoding. you need to adapt mult-con and mult-com but at the same time we need to adapt mult-sys, so as an experiment if things work out ok, just play a bit with mult-con/com e.g. replace a few harmless commands in the english interface and see if things work ok for persian footnote: voetnoot footnote fussnote poznamkapodcarou notapdp notasubsol notepdp eventually persian can become the 8th entry footnote: voetnoot somethingpersian fussnote poznamkapodcarou notapdp notasubsol notepdp \somethingpersian then should give you a footnote (we never really tested it with utf8 input so far) (when i have time i will (for luatex) make this mechanism different i.e. just lua tables from which i then can generate the con/com files) Hi Hans and everybody, I did as you said and saw two things. 1- The good news: it is possible to assign another name (even persian) for an option name. For example the word packed which is used as an option in some commands like \setupitemize works well if you substitute it with anything. 2- The bad news: names of commands (I mean words that is used in the input file with a backslash in front of them like footnote or setupsomething) are not well behaved if we change them in mult.con.tex. I tried to change for example the word footnote with a persian word with more than one character and in the running time I got the error that that command is not defined. But I was able to redefine footnote with a just one (persian) character. Thanks ___ 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 ___
[NTG-context] Persian interface
Hi everyone, I want to be able to use persian interface in context. So I tried to create two files cont-pe.xml and cont-pe.tex for this purpose. Now my questions are: 1- Am I supposed to just create these two files and then run context --make cont-pe. 2- Can context accept these two files in UTF-8 encoding. Thanks ___ 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 ___
Re: [NTG-context] Persian interface
Mehdi Omidali wrote: Hi everyone, I want to be able to use persian interface in context. So I tried to create two files cont-pe.xml and cont-pe.tex for this purpose. Now my questions are: 1- Am I supposed to just create these two files and then run context --make cont-pe. 2- Can context accept these two files in UTF-8 encoding. you need to adapt mult-con and mult-com but at the same time we need to adapt mult-sys, so as an experiment if things work out ok, just play a bit with mult-con/com e.g. replace a few harmless commands in the english interface and see if things work ok for persian footnote: voetnoot footnote fussnote poznamkapodcarou notapdp notasubsol notepdp eventually persian can become the 8th entry footnote: voetnoot somethingpersian fussnote poznamkapodcarou notapdp notasubsol notepdp \somethingpersian then should give you a footnote (we never really tested it with utf8 input so far) (when i have time i will (for luatex) make this mechanism different i.e. just lua tables from which i then can generate the con/com files) - 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 - ___ 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 ___
