Hi, I have found a glitch in lang-cjk.mkiv in definition of Japanese language name of days are shifted. It begins at line 136, sunday is actualy monday etc. In source code it looks like that: \setuplabeltext [\s!ja] [\v!sunday=月曜日] \setuplabeltext [\s!ja] [\v!monday=火曜日] \setuplabeltext [\s!ja] [\v!tuesday=水曜日] \setuplabeltext [\s!ja] [\v!wednesday=木曜日] \setuplabeltext [\s!ja] [\v!thursday=金曜日] \setuplabeltext [\s!ja] [\v!friday=土曜日] \setuplabeltext [\s!ja] [\v!saturday=日曜日] but it should be: \setuplabeltext [\s!ja] [\v!monday=月曜日] \setuplabeltext [\s!ja] [\v!tuesday=火曜日] \setuplabeltext [\s!ja] [\v!wednesday=水曜日] \setuplabeltext [\s!ja] [\v!thursday=木曜日] \setuplabeltext [\s!ja] [\v!friday=金曜日] \setuplabeltext [\s!ja] [\v!saturday=土曜日] \setuplabeltext [\s!ja] [\v!sunday=日曜日] Also I would like to ask if file lang-spe.mkii have some equivalent in MkIV and where the language specifics are defined (in which file)? Or is it treated in enco files? Thank you for answers. Tomas Pustelnik
On 3-5-2010 8:43, Tomáš Pustelník wrote:
Hi,
I have found a glitch in lang-cjk.mkiv in definition of Japanese language name of days are shifted. It begins at line 136, sunday is actualy monday etc. In source code it looks like that:
\setuplabeltext [\s!ja] [\v!sunday=月曜日] \setuplabeltext [\s!ja] [\v!monday=火曜日] \setuplabeltext [\s!ja] [\v!tuesday=水曜日] \setuplabeltext [\s!ja] [\v!wednesday=木曜日] \setuplabeltext [\s!ja] [\v!thursday=金曜日] \setuplabeltext [\s!ja] [\v!friday=土曜日] \setuplabeltext [\s!ja] [\v!saturday=日曜日]
but it should be:
\setuplabeltext [\s!ja] [\v!monday=月曜日] \setuplabeltext [\s!ja] [\v!tuesday=火曜日] \setuplabeltext [\s!ja] [\v!wednesday=水曜日] \setuplabeltext [\s!ja] [\v!thursday=木曜日] \setuplabeltext [\s!ja] [\v!friday=金曜日] \setuplabeltext [\s!ja] [\v!saturday=土曜日] \setuplabeltext [\s!ja] [\v!sunday=日曜日]
patched
Also I would like to ask if file lang-spe.mkii have some equivalent in MkIV and where the language specifics are defined (in which file)? Or is it treated in enco files?
in mkiv we don't have (want) language specifics ... why do yoi need them? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, May 06 2010, Hans Hagen wrote:
in mkiv we don't have (want) language specifics ... why do yoi need them?
Hello Hans, What is now the right mechanism, to trigger some setting when a specific language is activated and cancel this same setting, when this language is deactivated? Example: when entering French language, I want to execute "\setcharacterspacing[frenchpunctuation]" and when leaving French I want to execute "\setcharacterspacing[reset]". (today the file http://dl.contextgarden.net/modules/t-french/tex/context/third/french/t-fren... is broken, because I don't know how to do it right... :( Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/
On 7-5-2010 9:25, Peter Münster wrote:
On Thu, May 06 2010, Hans Hagen wrote:
in mkiv we don't have (want) language specifics ... why do yoi need them?
Hello Hans,
What is now the right mechanism, to trigger some setting when a specific language is activated and cancel this same setting, when this language is deactivated?
Example: when entering French language, I want to execute "\setcharacterspacing[frenchpunctuation]" and when leaving French I want to execute "\setcharacterspacing[reset]".
(today the file http://dl.contextgarden.net/modules/t-french/tex/context/third/french/t-fren... is broken, because I don't know how to do it right... :(
you can then probably just enable it as i cannot imagine a document which uses mixed typographical habits that still looks right anyway, there will be some mechanism but probably more at the level of the features itself (i.e. as part of setcharacterspacing) as there have to be ways to turn on/off specific language bound features. The mkii language specifics were mostly meant for encoding issues and those trigger points have disappeared as encodings are gone now. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Also I would like to ask if file lang-spe.mkii have some equivalent in MkIV and where the language specifics are defined (in which file)? Or is it treated in enco files?
in mkiv we don't have (want) language specifics ... why do yoi need them?
Hans
Well I actually don't need them, I browse source codes and I found it there. It looks quite useful so I was wondering, if in MkIV is this implemented as well. Could you please tell me, why specifics weren't implemented in MkIV (why don't we want them)? And is there any other mechanics which replace language specifics in MkIV? And just to be sure. In MkII language specifics are still working, right? Also are there any documents or information sources where I could find info about encoding in ConTeXt? I could use them for my bachelor thesis. Thank you for answer. Tomas Pustelnik
Am 06.05.10 22:16, schrieb Hans Hagen:
Also I would like to ask if file lang-spe.mkii have some equivalent in MkIV and where the language specifics are defined (in which file)? Or is it treated in enco files?
in mkiv we don't have (want) language specifics ... why do yoi need them?
languagespecifics are not needed but we need a method to load language dependend setups, e.g. for french you can have in lang-ger \startsetups [fr] [punctuation] \setcharacterspacing[frenchpunctuation] \stopsetups \startsetups [fr] [itemize] \setupitemize[symbol=2] \stopsetups and in your document you can load them with \setuplanguage[fr][setups={punctuation,itemize}] or \enablelanguagesetups[punctuation,itemize] Wolfgang
On 9-5-2010 10:47, Wolfgang Schuster wrote:
Am 06.05.10 22:16, schrieb Hans Hagen:
Also I would like to ask if file lang-spe.mkii have some equivalent in MkIV and where the language specifics are defined (in which file)? Or is it treated in enco files?
in mkiv we don't have (want) language specifics ... why do yoi need them?
languagespecifics are not needed but we need a method to load language dependend setups, e.g. for french you can have in lang-ger
\startsetups [fr] [punctuation]
\setcharacterspacing[frenchpunctuation]
\stopsetups
\startsetups [fr] [itemize]
\setupitemize[symbol=2]
\stopsetups
and in your document you can load them with
\setuplanguage[fr][setups={punctuation,itemize}]
or
\enablelanguagesetups[punctuation,itemize]
indeed setups is the way to go \enablelanguagesetups is somewhat tricky as we then also want to disable them selectively which boils down to either tagging them all internally or let lua deal with sets in which case we need some optimization to prevent redundant calls also, we need the reverse actions then i.e. for german we want to disable the punctuation \startsetups [fr] [punctuation:reset] \resetcharacterspacing \stopsetups and for style changes that's quite some extra code (and adding an extra level of language hashes to each mechanism is also no solution) so, we might distinguish between 'mainlanguage' and local 'language' \startlanguagesetups [fr:punctuation:set] % local language \setcharacterspacing[frenchpunctuation] \stopsetups \startlanguagesetups [fr:punctuation:reset] % local language \resetcharacterspacing \stopsetups \startlanguagesetups [fr:itemize] % mainlanguage \setupitemize[symbol=2] \stopsetups or so ... needs bit of thinking Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (4)
-
Hans Hagen -
Peter Münster -
Tomáš Pustelník -
Wolfgang Schuster