Re: [NTG-context] Problem with Encoding math symbols
On 10-1-2011 4:46, Anand Raj wrote: Hi, I have xml containing following mathml. The Ω is symbol replaced with * #937;* in the xml. But when i run the tex file. The pdf is not rendered with Ω symbol this work sok in the beta (but another error occurred there, one that has been slumbering there for a while) ... so, i uploaded a new beta 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 - ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Problem with Encoding math symbols
Hi, I have xml containing following mathml. The Ω is symbol replaced with * #937;* in the xml. But when i run the tex file. The pdf is not rendered with Ω symbol. I have enclosed my xml and tex files. Suppose that math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true miS/mi mo=/mo mn11/mn mo*#937;*/mo mo,/mo miT/mi mo=/mo mn90/mn mo#937;/mo mrow mtextand/mtext /mrow miU/mi mo=/mo mn84/mn mo#937;/mo /mstyle /math. Thanks Anand ?xml version=1.0 encoding=UTF-8? documentdiv class='question' divp/pbr/br/ Simplify the expression br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mfrac mrow mn2/mn msup miy/mi mn4/mn /msup /mrow mrow mix/mi miy/mi mn-4/mn miy/mi /mrow /mfrac /mstyle /mathbr/ and give your answer in the form of br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mfrac mrow mrow mif/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow mrow mrow mig/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow /mfrac mo./mo /mstyle /mathbr/ br/ Your answer for the function math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mrow mif/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mstyle /math is : __ br/ Your answer for the function math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mrow mig/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mstyle /math is : __ br//div /divdiv class='question' divp/pbr/br/ Simplify the expression br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mfrac mrow msup mix/mi mn2/mn /msup mn-8/mn mix/mi mn+12/mn /mrow mrow msup mix/mi mn2/mn /msup mn-3/mn mix/mi mn+2/mn /mrow /mfrac /mstyle /mathbr/ and give your answer in the form of br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mfrac mrow mrow mif/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow mrow mrow mig/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow /mfrac mo./mo /mstyle /mathbr/ br/ Your answer for the function math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mrow mif/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mstyle /math is : __ br/ Your answer for the function math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mrow mig/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mstyle /math is : __ br//div /divdiv class='question' divp/pbr/br/ Simplify the expression br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mfrac mrow mn2/mn mix/mi mn-2/mn /mrow mrow mix/mi mn-1/mn /mrow /mfrac mo+/mo mfrac mrow mn2/mn mo-/mo mix/mi /mrow mrow mix/mi mn-1/mn /mrow /mfrac /mstyle /mathbr/ and give your answer in the form of br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mfrac mrow mrow mif/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow mrow mrow mig/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow /mfrac mo./mo /mstyle /mathbr/ br/ Your answer for the function math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mrow mif/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mstyle /math is : __ br/ Your answer for the function math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mrow mig/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mstyle /math is : __ br//div /divdiv class='question' divp/pbr/br/ Simplify the expression br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mn3/mn mo-/mo mfrac mrow mn5/mn /mrow mrow mix/mi mn-4/mn /mrow /mfrac /mstyle /mathbr/ and give your answer in the form of br/math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mfrac mrow mrow mif/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow mrow mrow mig/mi mrow mo(/mo mix/mi mo)/mo /mrow /mrow /mrow /mfrac mo./mo /mstyle /mathbr/ br/ Your answer for the function math xmlns=http://www.w3.org/1998/Math/MathML; mstyle displaystyle=true mrow mif/mi mrow mo(/mo
[NTG-context] Problem with encoding
Hello,
this example stopped working. I don't know exactly when, maybe with the newest
Ctx beta. Let's have two sources:
--- t.mkiv
\mainlanguage[cz]
\enableregime[cp1250]
\starttext
\input t2.mkiv
AáSš
\stoptext
---
And:
--- t2.mkiv
AáSš
---
The t2.mkiv is included by the main file t.mkiv.
The strange thing is that chars with diacritics being used in the included file
are successfully processed, whilst those in the main file are not.
Here's the process log:
---
MTXrun | run 1: luatex
--fmt=c:/ConTeXt/tex/texmf-cache/luatex-cache/context/f53042fa2e1c106bc7e3383ec8c3a00c/formats/cont-en
--lua=c:/ConTeXt/tex/texmf-cache/luatex-cache/context/f53042fa2e1c106bc7e3383ec8c3a00c/formats/cont-en.lui
--backend=pdf C:/Lukas/Jobs/Holesov.PDPS/SO_201/Texts/T/t.mkivThis is LuaTeX, Version
beta-0.64.0-2010111223 (rev 3956)
\write18 enabled.
(C:/Lukas/Jobs/Holesov.PDPS/SO_201/Texts/T/t.mkiv
ConTeXt ver: 2010.11.27 14:27 MKIV fmt: 2010.11.29 int: english/english
system : cont-new loaded
(c:/ConTeXt/tex/texmf-context/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
(c:/ConTeXt/tex/texmf-context/tex/context/base/cont-new.mkiv))
system : cont-fil.mkiv loaded
(c:/ConTeXt/tex/texmf-context/tex/context/base/cont-fil.mkiv
loading : ConTeXt File Synonyms
)
system : cont-sys.rme loaded
(c:/ConTeXt/tex/texmf-context/tex/context/user/cont-sys.rme
(c:/ConTeXt/tex/texmf-context/tex/context/base/type-def.mkiv)
(c:/ConTeXt/tex/texmf-context/tex/context/base/type-lua.mkiv)
(c:/ConTeXt/tex/texmf-context/tex/context/base/type-siz.mkiv)
(c:/ConTeXt/tex/texmf-context/tex/context/base/type-otf.mkiv))
system : cont-err loaded
(c:/ConTeXt/tex/texmf-context/tex/context/base/cont-err.tex
systems : no file 'cont-sys.tex', using 'cont-sys.rme' instead
)
system : t.top loaded
(t.top
){c:/ConTeXt/tex/texmf/fonts/map/dvips/lm/lm-math.map}{c:/ConTeXt/tex/texmf/fonts/map/dvips/lm/lm-rm.map}{c:/ConTeXt/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
bodyfont: 12pt rm is loaded
fonts : preloading latin modern fonts (first stage)
language: language en is active
publications: loading formatting style from bxml-apa
(c:/ConTeXt/tex/texmf-context/tex/context/base/bxml-apa.mkiv)
systems : begin file C:/Lukas/Jobs/Holesov.PDPS/SO_201/Texts/T/t.mkiv
at line 4
(t2.mkiv)
! String contains an invalid utf-8 sequence.
l.7 A
ßSÜ
backends using xmp file
'c:/ConTeXt/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pagesflushing realpage 1, userpage 1, subpage 1
systems : end file C:/Lukas/Jobs/Holesov.PDPS/SO_201/Texts/T/t.mkiv at
line 8
)c:/ConTeXt/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
mkiv lua stats : used config file -
c:/ConTeXt/tex/texmf/web2c/texmfcnf.lua
mkiv lua stats : used cache path -
c:/ConTeXt/tex/texmf-cache/luatex-cache/context/f53042fa2e1c106bc7e3383ec8c3a00c
mkiv lua stats : input load time - 0.016 seconds
mkiv lua stats : stored bytecode data - 257 modules, 56 tables, 313 chunks
mkiv lua stats : cleaned up reserved nodes - 33 nodes, 9 lists of 411
mkiv lua stats : node memory usage - 19 glue_spec
mkiv lua stats : node list callback tasks - 6 unique task lists, 5 instances
(re)created, 329 calls
mkiv lua stats : used backend - pdf (backend for directly
generating pdf output)
mkiv lua stats : loaded patterns - cs::23 en::2
mkiv lua stats : callbacks - direct: 481, indirect: 4508,
total: 4989
mkiv lua stats : lxml preparation time - 0.000 seconds, 0 nodes, 11 lpath
calls, 0 cached calls
mkiv lua stats : result saved in file - t.pdf
mkiv lua stats : loaded fonts - 33 files: stmary10.afm
lmmono12-regular.otf lmmono8-regular.otf lmmono9-regular.otf lmroman12-bold.otf
lmroman12-regular.otf lmroman7-bold.otf lmroman7-regular.otf lmroman9-bold.otf
lmroman9-regular.otf lmsans12-regular.otf lmsans8-regular.otf
lmsans9-regular.otf eufb10.tfm eufb7.tfm eufm10.tfm eufm7.tfm msam10.tfm
msam7.tfm msbm10.tfm msbm7.tfm lmex10.tfm lmmi12.tfm lmmi7.tfm lmmi9.tfm
lmmib10.tfm lmmib7.tfm lmsy10.tfm lmsy7.tfm lmsy9.tfm rm-lmr12.tfm rm-lmr7.tf
m rm-lmr9.tfm
mkiv lua stats : fonts load time - 0.266 seconds
mkiv lua stats : luatex banner - this is luatex, version
beta-0.64.0-2010111223 (web2c 2010) (rev 3956)
mkiv lua stats : control sequences - 29979 of 165536
mkiv lua stats : current memory usage - 32 MB (ctx: 32 MB)
mkiv lua stats : runtime - 0.813 seconds, 1 processed pages,
1 shipped pages, 1.230 pages/second
MTXrun | fatal error: return code: 1
---
So the example doesn't work with the Ctx version from 27.11.2010. But it does
with one from 20.11.2010 (tested on another computer).
So is it possible to make Ctx work even when diacritics and ANSI encoding is
used
Re: [NTG-context] Problem with encoding
2010/12/21 Procházka Lukáš Ing. - Pontex s. r. o. wrote: \mainlanguage[cz] (unrelated to your question, but ...) It should probably be cs, not cz. Isn't cz country code and cs language code? The cz is left for backward compatibility reasons. Mojca ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
Hello, On Tue, 21 Dec 2010 10:29:13 +0100, Mojca Miklavec mojca.miklavec.li...@gmail.com wrote: 2010/12/21 Procházka Lukáš Ing. - Pontex s. r. o. wrote: \mainlanguage[cz] It should probably be cs, not cz. I'm getting the same error message even with cs. Isn't cz country code and cs language code? BTW: What is the difference what the COUNTRY code and the LANGUAGE code affects? Lukas The cz is left for backward compatibility reasons. Mojca -- Ing. Lukáš Procházka [mailto:l...@pontex.cz] Pontex s. r. o. [mailto:pon...@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038 ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
Isn't cz country code and cs language code? Indeed -- although it doesn't make much sense that cs be the language code for a language name spelt Czech in English and česky in Czech (I suspect it's related to the fact that cs was also the country code for Czechoslovakia in its time, so that the same code was used for the main language of that country, so to say). Arthur ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
On 21-12-2010 10:37, Procházka Lukáš Ing. - Pontex s. r. o. wrote: Hello, On Tue, 21 Dec 2010 10:29:13 +0100, Mojca Miklavec mojca.miklavec.li...@gmail.com wrote: 2010/12/21 Procházka Lukáš Ing. - Pontex s. r. o. wrote: \mainlanguage[cz] It should probably be cs, not cz. one can always use 'czech' I'm getting the same error message even with cs. Regimes were dealt with at the file level but it has to be at the line level for in-document switching. I uploaded a beta: - m-database fix - regimes fix - split numbering fix 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 - ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
BTW: What is the difference what the COUNTRY code and the LANGUAGE code affects? In your case, you should use a language code since you want to set a language. ConTeXt has used different sets of codes in the past, but we now try to follow IETF recommendation Tag for Identifying Languages (http://tools.ietf.org/html/bcp47), because it's the only one that can be precise enough for our needs (at least among the tagging systems I know of). For example, you can distinguish between British English and American English by appending a country code to the language code (hence en-gb and en-us, respectively). Using a country code to identify a language is generally a bad idea and should be discouraged, since that's not what they're meant for, and it can lead to confusion: for example, you could use the code uk to identify English as spoken in the United Kingdom, but that's actually the language code for Ukrainian, which has been an actual problem for ConTeXt in the post (in addition to that, uk is not even the proper language code for the United Kingdom: it's gb, as written above; the reason why uk is used as a DNS top-level domain is not clear and has lead, alas, to even more confusion). The authorities that decide upon language and country codes are different committees of the ISO; the ISO standard for language codes is ISO 639 (with different parts), and the one for country codes is ISO 3166 (again, with different parts; the two-letter codes of ISO 3166-1 are generally rather well-known because they're the ones being used for DNS top-level domains -- with some exceptions, see above). Arthur ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
2010/12/21 Procházka Lukáš Ing. - Pontex s. r. o. l...@pontex.cz: It should probably be cs, not cz. I'm getting the same error message even with cs. As I said: my comment was unrelated to your problem. Isn't cz country code and cs language code? BTW: What is the difference what the COUNTRY code and the LANGUAGE code affects? If you were a citizen of Austria or Switzerlad, you would not be able to use \mainlanguage[at] or \mainlanguage[ch] You need to use [de] instead (which happens to be the same as country code for Germany, but that is just a coincidence). Country codes usually have no meaning to ConTeXt. In the case of Czech it is just for the sake of backward-compatibility that cz works. Mojca ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
... OK, thanks all for the answers and fixes. Lukas On Tue, 21 Dec 2010 11:11:33 +0100, Arthur Reutenauer arthur.reutena...@normalesup.org wrote: BTW: What is the difference what the COUNTRY code and the LANGUAGE code affects? In your case, you should use a language code since you want to set a language. ConTeXt has used different sets of codes in the past, but we now try to follow IETF recommendation Tag for Identifying Languages (http://tools.ietf.org/html/bcp47), because it's the only one that can be precise enough for our needs (at least among the tagging systems I know of). For example, you can distinguish between British English and American English by appending a country code to the language code (hence en-gb and en-us, respectively). Using a country code to identify a language is generally a bad idea and should be discouraged, since that's not what they're meant for, and it can lead to confusion: for example, you could use the code uk to identify English as spoken in the United Kingdom, but that's actually the language code for Ukrainian, which has been an actual problem for ConTeXt in the post (in addition to that, uk is not even the proper language code for the United Kingdom: it's gb, as written above; the reason why uk is used as a DNS top-level domain is not clear and has lead, alas, to even more confusion). The authorities that decide upon language and country codes are different committees of the ISO; the ISO standard for language codes is ISO 639 (with different parts), and the one for country codes is ISO 3166 (again, with different parts; the two-letter codes of ISO 3166-1 are generally rather well-known because they're the ones being used for DNS top-level domains -- with some exceptions, see above). Arthur -- Ing. Lukáš Procházka [mailto:l...@pontex.cz] Pontex s. r. o. [mailto:pon...@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038 ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
If you were a citizen of Austria or Switzerlad, you would not be able to use \mainlanguage[at] or \mainlanguage[ch] As it happens, at is not the ISO 639 code of any language (and it's doubtful it will be in the near future), but ch is the code for Chamorro (http://www.ethnologue.com/show_language.asp?code=cha), so you would indeed have problems :-) Arthur ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
On 2010-12-21 11:11:33, Arthur Reutenauer wrote: BTW: What is the difference what the COUNTRY code and the LANGUAGE code affects? In your case, you should use a language code since you want to set a language. ConTeXt has used different sets of codes in the past, but we now try to follow IETF recommendation Tag for Identifying Languages (http://tools.ietf.org/html/bcp47), because it's the only one that can be precise enough for our needs (at least among the tagging systems I know of). For example, you can distinguish between British English and American English by appending a country code to the language code (hence en-gb and en-us, respectively). Using a country code to identify a language is generally a bad idea and should be discouraged, since that's not what they're meant for, and it can lead to confusion: for example, you could use the code uk to identify English as spoken in the United Kingdom, but that's actually the language code for Ukrainian, which has been an actual problem for ConTeXt in the post (in addition to that, uk is not even the proper language code for the United Kingdom: it's gb, as written above; the reason why uk is used as a DNS top-level domain is not clear and has lead, alas, to even more confusion). But context uses some non-standard codes also: “deo” instead of “de-1901” for sane German orthography, and “agr” for ancient Attic instead of “grc” or “el-polyton”. (Testfile appended.) Philipp PS: nice tools http://people.w3.org/rishida/utils/subtags/ http://unicode.org/cldr/utility/languageid.jsp The authorities that decide upon language and country codes are different committees of the ISO; the ISO standard for language codes is ISO 639 (with different parts), and the one for country codes is ISO 3166 (again, with different parts; the two-letter codes of ISO 3166-1 are generally rather well-known because they're the ones being used for DNS top-level domains -- with some exceptions, see above). Arthur ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___ -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments pgpxPS0SIuQHZ.pgp Description: PGP signature ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
On 2010-12-21 12:19:15, Philipp Gesang wrote:
Attic instead of “grc” or “el-polyton”. (Testfile appended.)
Sorry for the mess, test file *now* appended …
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
% http://unicode.org/cldr/utility/languageid.jsp?a=de-1901l=en
\setuppapersize [XY][A4] \setuppaper [nx=2,ny=2] \setuparranging [XY]
\usetypescriptfile[type-cmu] \setupbodyfont[computer-modern-unicode,10pt]
\mainlanguage[de-1901]
%\mainlanguage[deo]
\starttext
\startcolumns[n=2]
\dorecurse{4}{%
\bgroup
%\language[deo]% currently used language code, context only
\language[de-1901] % BCP-47
Seitens der Kritik habe ich auch gar nichts anderes erwartet, als daß
meist von „Szene“ gesprochen wird. Die Ursache dafür ist eben in der
Tradition des deutschen Pathos zu ermitteln, welches den symphonischen
Begriff im allgemeinen stempelt. Ebendeshalb habe ich diesen Aufsatz
über meine Sinfonie geschrieben, um den Beweis zu erbringen, daß ich das
Pathos gänzlich ablehne, was auch eine entsprechende Verringerung des
gesamten Orchesterapparats bedeutet und daß ich mich mit dem Begriff
„Sinfonie“ gänzlich anders auseinandersetze als die übrigen Komponisten,
welche traditiongemäß fruchtlos fortsetzen, wo tatsächlich Bruckner und
Mahler bereits aufhörten. Als Komponist dieses Werkes kann ich mich
jederzeit rechtfertigen und verantworte voll und ganz den Titel
„Sinfonie“.
Im übrigen möchte ich bemerken, daß die heute in Deutschland usuelle
„Neue Sachlichkeit“ keineswegs der Wahrheit und Notwendigkeit
entspringt, da der Deutsche nie aus seiner Sentimentalität herauskann.
Die augenblickliche Bach- und Händelrennaissance ist nichts anderes als
ein Zeichen von Impotenz, welche mit dem Schlagwort „Neue Sachlichkeit“
bemäntelt wird. Der Fall Strawinsky ist dafür eklatant und der nächste
fall wird die Erstarrung Hindemiths werden, falls dieser nicht
rechtzeitig aus der Schablone herausfindet.
{\em Erwin Schulhoff} 1928\par
\egroup
\bgroup
%\language[agr]
\language[grc]
τούτων δὲ ὑπαρχόντων αὖ πᾶσα ἀνάγκη τόνδε τὸν κόσμον εἰκόνα
τινὸς εἶναι. μέγιστον δὴ παντὸς ἄρξασθαι κατὰ φύσιν ἀρχήν. ὧδε
οὖν περί τε εἰκόνος καὶ περὶ τοῦ παραδείγματος αὐτῆς
διοριστέον, ὡς ἄρα τοὺς λόγους, ὧνπέρ εἰσιν ἐξηγηταί, τούτων
αὐτῶν καὶ συγγενεῖς ὄντας· τοῦ μὲν οὖν μονίμου καὶ βεβαίου καὶ
μετὰ νοῦ καταφανοῦς μονίμους καὶ ἀμεταπτώτους –καθ᾽ ὅσον οἷόν
τε καὶ ἀνελέγκτοις προσήκει λόγοις εἶναι καὶ ἀνικήτοις, τούτου
δεῖ μηδὲν ἐλλείπειν– τοὺς δὲ τοῦ πρὸς μὲν ἐκεῖνο
ἀπεικασθέντος, ὄντος δὲ εἰκόνος εἰκότας ἀνὰ λόγον τε ἐκείνων
ὄντας· ὅτιπερ πρὸς γένεσιν οὐσία, τοῦτο πρὸς πίστιν ἀλήθεια.
{\language[deo]\em Plat. Tim. 29bc}\par
\egroup
}
\stopcolumns
\stoptext
pgplcDC2ICfuU.pgp
Description: PGP signature
___
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Problem with encoding
On Tue, 21 Dec 2010 12:19:15 +0100 Philipp Gesang pges...@ix.urz.uni-heidelberg.de wrote: But context uses some non-standard codes also: deo instead of de-1901 for sane German orthography, and agr for ancient Attic instead of grc or el-polyton. (Testfile appended.) Yes, we should make grc a synonym of agr. el-polyton is, AFAIK, modern polytonic Greek, which is not the same. Thomas ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
But context uses some non-standard codes also: “deo” instead of “de-1901” for sane German orthography, and “agr” for ancient Attic instead of “grc” or “el-polyton”. (Testfile appended.) Yes, that's what I said: ConTeXt has used non-standard codes in the past, now we try to follow BCP 47, while attempting to stay backward-compatible, and providing easy-to-remember names for the user as well. But of course, it's always easier to write a three-line sentence that contains one troll and one severe inaccuracy. http://unicode.org/cldr/utility/languageid.jsp Note that Unicode Language Identifiers are not the same as BCP 47 tags, even if they're very close in their goals and shape. Arthur ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
Yes, we should make grc a synonym of agr. el-polyton is, AFAIK, modern polytonic Greek, which is not the same. Obviously so. Amusingly, ISO states that el is meant for the Greek language after the Fall of Constantinople(*), which assigns a rather long period to Ancient Greek. Note that for all I know, there is no way to distinguish katharevousa from demotic; but it would certainly be added to the IETF registry if someone applied for it. Arthur (*) Of course it doesn't say after the Fall of Constanople that way, it says from 1453 onwards (http://www.sil.org/iso639-3/documentation.asp?id=ell) but that's clearly what is meant. ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
On 21-12-2010 1:23, Arthur Reutenauer wrote: (*) Of course it doesn't say after the Fall of Constanople that way, it says from 1453 onwards (http://www.sil.org/iso639-3/documentation.asp?id=ell) but that's clearly what is meant. given some historic disputes on tex mailing list we should be glad that they avoided a reference to macedonian times 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 - ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding
On 21-12-2010 12:19, Philipp Gesang wrote: But context uses some non-standard codes also: “deo” instead of deo = de old (and no one objected at that point) when context was dutch only we used 'du' as that's the abbreviation used in schools 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 - ___ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Problem with encoding, XML and writetolist...
Hi Hans and Vit,
I've attached pdf and tex made with texexec 8bit.tex using the last beta
(with cp1250 regime). The version chapterB is what I am using now, chapterA
version is straightforward but not functional.
From this my ideas from last mail came -- when I am expanding \XMLflush
exactly and controlled, result is OK (the expansion stops before active
characters start to expand.
IMHO, the solution on character level is something different (although it works
:-); yes, I did not study Vit's problems from year before. I never had a
problems with simple TeX (\chapter{čřžý}), only with XML :-), so for me it
would be sufficient solve XML level. Of course, if it is stuff of other level,
it cannot be solved in XML.
Thanks, Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Hans Hagen
Sent: Wednesday, April 05, 2006 1:03 PM
To: mailing list for ConTeXt users
Subject: Re: [NTG-context] Problem with encoding, XML and writetolist...
Vit Zyka wrote:
Martin Kolařík wrote:
Hi Hans,
I've analyzed the situation using different combinations of regimes and
encodings, including switching off handling (\donothandleactivecharacter)
and it seems to me, that every text with chars 127, which is fully
expanded (as in 8bit.tex), must cause difficulties, because TOC entry read
back from TUO is scanned independently and thus spaces are gobbled.
Hi Martin,
we have discussed this problem a year ago. In that time I solve it just
writing '{}' in each title where was needed, like
\chapter{Dobré{} ráno}
Now I have cooked an automatic solution. It is not optimal (effective)
but working. The only needs is to redefine
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
and to load appropriate encoding file once more. Since it is banned a
new macro \reuseencoding was introduce:
For Hans:
It would be nice if this feature was enabled in a standard distro.
Perhaps you will find some more optimal solution...
---
\unprotected
\def\doreuseencoding#1%
{\letvalue{\c!file\f!encodingprefix#1}\empty
\makeshortfilename[\f!encodingprefix#1]%
\startreadingfile
\readsysfile\shortfilename
{\showmessage\m!encodings2{#1}}
{\showmessage\m!encodings3{#1}}%
\stopreadingfile}
\def\reuseencoding[#1]%
{\processcommalist[#1]\doreuseencoding}
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
\reuseencoding[ec]
\enableregime[latin2]
\starttext
\writetolist[chapter]{1}{Dobré ráno}
\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
\placecontent
\stoptext
the {} may break liguature building (and maybe kerning) ... taco knows ...
I got a brainwave ...
\enableregime[latin2]
\starttext
\def\numcharacter#1{\rawcharacter{#1}}%
\let\dochar\numcharacter
\writetolist[chapter]{1}{Dobré ráno}
\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
\placelist[chapter][criterium=text]
test
\typefile{test.tuo}
\stoptext
this can be sped up (a bit) with
% \dostepwiserecurse{0}{255}{1}
% {\setevalue{rchr:\recurselevel}{\rawcharacter\recurselevel}}
% \def\rawcharacter#1{\getvalue{rchr:#1}}
this means that all chars are round tripped to themselves in output files!
raw characters are not active and they are therefore equivalent to \char
it's enough then to put
\def\numcharacter#1{\rawcharacter{#1}}%
\let\dochar\numcharacter
into cont-new.tex
(i will discuss this in more detail with taco later)
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
8bit.pdf
Description: Adobe PDF document
8bit.tex
Description: Binary data
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Hi Hans,
I've analyzed the situation using different combinations of regimes and
encodings, including switching off handling (\donothandleactivecharacter) and
it seems to me, that every text with chars 127, which is fully expanded (as
in 8bit.tex), must cause difficulties, because TOC entry read back from TUO is
scanned independently and thus spaces are gobbled.
Now I have solved it using not-stable solution -- I am using triple sequence of
\expandafter to expand \XMLflush after \chapter instead \expanded. The solution
is not stable as it is ConTeXt implementation dependent.
On the other side, now I do not know, how to partially expand code
\chaper{\XMLflush{XMLTag}} to obtain sequence of simple unexpanded chars.
Simple \expandafter is not sufficient, more \expandafters is dirty trick and
full expansion (\expanded) leads to TOC entry problem. In TeX source this
cannot occur (or can occur in strange situations :-), in XML source this is
almost rule.
Maybe it would be useful to have in XML engine macro, which expands XMLdata
exactly to get read (original) content (like mine triple \expandafter). Maybe
such macro already exists and I am a real fool :-)
Thank you for help, have a nice day,
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Hans Hagen
Sent: Monday, April 03, 2006 11:57 AM
To: [EMAIL PROTECTED]; mailing list for ConTeXt users
Subject: Re: [NTG-context] Problem with encoding, XML and writetolist...
Martin Kolařík wrote:
Aha, here maybe will be the solution :-)
I'am using standalone Win32 distribution from Pragma and I'm
running texexec with --translate=cp1252cs. Typescripts use il2,
which corresponds to fonts, of course. If I run the code without
XML (if I transcribe XML to \chapter etc.) I get toc entry correctly too.
Where should I look for more? What is natural.ctx?
this is a one-to-one translation vector, and the one standard
used by context; forget about all those other mappings, they can
be done using regimes; you can use an il2 input regime, and any
(resonable) font encoding,
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://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] Problem with encoding, XML and writetolist...
Hi Hans,
I've analyzed the situation using different combinations of regimes and
encodings, including switching off handling (\donothandleactivecharacter) and
it seems to me, that every text with chars 127, which is fully expanded (as
in 8bit.tex), must cause difficulties, because TOC entry read back from TUO is
scanned independently and thus spaces are gobbled.
Now I have solved it using not-stable solution -- I am using triple sequence of
\expandafter to expand \XMLflush after \chapter instead \expanded. The solution
is not stable as it is ConTeXt implementation dependent.
On the other side, now I do not know, how to partially expand code
\chaper{\XMLflush{XMLTag}} to obtain sequence of simple unexpanded chars.
Simple \expandafter is not sufficient, more \expandafters is dirty trick and
full expansion (\expanded) leads to TOC entry problem. In TeX source this
cannot occur (or can occur in strange situations :-), in XML source this is
almost rule.
Maybe it would be useful to have in XML engine macro, which expands XMLdata
exactly to get read (original) content (like mine triple \expandafter). Maybe
such macro already exists and I am a real fool :-)
Thank you for help, have a nice day,
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Hans Hagen
Sent: Monday, April 03, 2006 11:57 AM
To: [EMAIL PROTECTED]; mailing list for ConTeXt users
Subject: Re: [NTG-context] Problem with encoding, XML and writetolist...
Martin Kolařík wrote:
Aha, here maybe will be the solution :-)
I'am using standalone Win32 distribution from Pragma and I'm
running texexec with --translate=cp1252cs. Typescripts use il2,
which corresponds to fonts, of course. If I run the code without
XML (if I transcribe XML to \chapter etc.) I get toc entry correctly too.
Where should I look for more? What is natural.ctx?
this is a one-to-one translation vector, and the one standard
used by context; forget about all those other mappings, they can
be done using regimes; you can use an il2 input regime, and any
(resonable) font encoding,
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://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] Problem with encoding, XML and writetolist...
Martin Kolařík wrote:
Hi Hans,
I've analyzed the situation using different combinations of regimes and
encodings, including switching off handling (\donothandleactivecharacter) and
it seems to me, that every text with chars 127, which is fully expanded (as
in 8bit.tex), must cause difficulties, because TOC entry read back from TUO
is scanned independently and thus spaces are gobbled.
Now I have solved it using not-stable solution -- I am using triple sequence
of \expandafter to expand \XMLflush after \chapter instead \expanded. The
solution is not stable as it is ConTeXt implementation dependent.
On the other side, now I do not know, how to partially expand code
\chaper{\XMLflush{XMLTag}} to obtain sequence of simple unexpanded chars.
Simple \expandafter is not sufficient, more \expandafters is dirty trick and
full expansion (\expanded) leads to TOC entry problem. In TeX source this
cannot occur (or can occur in strange situations :-), in XML source this is
almost rule.
Maybe it would be useful to have in XML engine macro, which expands XMLdata
exactly to get read (original) content (like mine triple \expandafter). Maybe
such macro already exists and I am a real fool :-)
Thank you for help, have a nice day,
some commands indeed have keys like:
expansion=no|yes|utf|xml|command
and alike
the problem is that when one does something \expanded{...} in a style, it
bypasses this mechanism
can you make me a (as small as possible) example of a doc? i can then test it
here with my version
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Martin Kolařík wrote:
Hi Hans,
I've analyzed the situation using different combinations of regimes and
encodings, including switching off handling (\donothandleactivecharacter) and
it seems to me, that every text with chars 127, which is fully expanded (as
in 8bit.tex), must cause difficulties, because TOC entry read back from TUO
is scanned independently and thus spaces are gobbled.
Hi Martin,
we have discussed this problem a year ago. In that time I solve it just
writing '{}' in each title where was needed, like
\chapter{Dobré{} ráno}
Now I have cooked an automatic solution. It is not optimal (effective)
but working. The only needs is to redefine
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
and to load appropriate encoding file once more. Since it is banned a
new macro \reuseencoding was introduce:
For Hans:
It would be nice if this feature was enabled in a standard distro.
Perhaps you will find some more optimal solution...
---
\unprotected
\def\doreuseencoding#1%
{\letvalue{\c!file\f!encodingprefix#1}\empty
\makeshortfilename[\f!encodingprefix#1]%
\startreadingfile
\readsysfile\shortfilename
{\showmessage\m!encodings2{#1}}
{\showmessage\m!encodings3{#1}}%
\stopreadingfile}
\def\reuseencoding[#1]%
{\processcommalist[#1]\doreuseencoding}
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
\reuseencoding[ec]
\enableregime[latin2]
\starttext
\writetolist[chapter]{1}{Dobré ráno}
\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
\placecontent
\stoptext
---
Now I have solved it using not-stable solution -- I am using triple sequence
of \expandafter to expand \XMLflush after \chapter instead \expanded. The
solution is not stable as it is ConTeXt implementation dependent.
On the other side, now I do not know, how to partially expand code
\chaper{\XMLflush{XMLTag}} to obtain sequence of simple unexpanded chars.
Simple \expandafter is not sufficient, more \expandafters is dirty trick and
full expansion (\expanded) leads to TOC entry problem. In TeX source this
cannot occur (or can occur in strange situations :-), in XML source this is
almost rule.
Maybe it would be useful to have in XML engine macro, which expands XMLdata
exactly to get read (original) content (like mine triple \expandafter). Maybe
such macro already exists and I am a real fool :-)
Thank you for help, have a nice day,
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Hans Hagen
Sent: Monday, April 03, 2006 11:57 AM
To: [EMAIL PROTECTED]; mailing list for ConTeXt users
Subject: Re: [NTG-context] Problem with encoding, XML and writetolist...
Martin Kolařík wrote:
Aha, here maybe will be the solution :-)
I'am using standalone Win32 distribution from Pragma and I'm
running texexec with --translate=cp1252cs. Typescripts use il2,
which corresponds to fonts, of course. If I run the code without
XML (if I transcribe XML to \chapter etc.) I get toc entry correctly too.
Where should I look for more? What is natural.ctx?
this is a one-to-one translation vector, and the one standard
used by context; forget about all those other mappings, they can
be done using regimes; you can use an il2 input regime, and any
(resonable) font encoding,
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
--
===
Ing. Vít Zýka, Ph.D. TYPOkvítek
database publishing databazove publikovani
data maintaining and typesetting in typographic quality
priprava dat a jejich sazba v typograficke kvalite
tel.: (+420) 777 198 189 www: http://typokvitek.com
===
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Vit Zyka wrote:
Martin Kolařík wrote:
Hi Hans,
I've analyzed the situation using different combinations of regimes and
encodings, including switching off handling (\donothandleactivecharacter)
and it seems to me, that every text with chars 127, which is fully
expanded (as in 8bit.tex), must cause difficulties, because TOC entry read
back from TUO is scanned independently and thus spaces are gobbled.
Hi Martin,
we have discussed this problem a year ago. In that time I solve it just
writing '{}' in each title where was needed, like
\chapter{Dobré{} ráno}
Now I have cooked an automatic solution. It is not optimal (effective)
but working. The only needs is to redefine
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
and to load appropriate encoding file once more. Since it is banned a
new macro \reuseencoding was introduce:
For Hans:
It would be nice if this feature was enabled in a standard distro.
Perhaps you will find some more optimal solution...
---
\unprotected
\def\doreuseencoding#1%
{\letvalue{\c!file\f!encodingprefix#1}\empty
\makeshortfilename[\f!encodingprefix#1]%
\startreadingfile
\readsysfile\shortfilename
{\showmessage\m!encodings2{#1}}
{\showmessage\m!encodings3{#1}}%
\stopreadingfile}
\def\reuseencoding[#1]%
{\processcommalist[#1]\doreuseencoding}
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
\reuseencoding[ec]
\enableregime[latin2]
\starttext
\writetolist[chapter]{1}{Dobré ráno}
\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
\placecontent
\stoptext
the {} may break liguature building (and maybe kerning) ... taco knows ...
I got a brainwave ...
\enableregime[latin2]
\starttext
\def\numcharacter#1{\rawcharacter{#1}}%
\let\dochar\numcharacter
\writetolist[chapter]{1}{Dobré ráno}
\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
\placelist[chapter][criterium=text]
test
\typefile{test.tuo}
\stoptext
this can be sped up (a bit) with
% \dostepwiserecurse{0}{255}{1}
% {\setevalue{rchr:\recurselevel}{\rawcharacter\recurselevel}}
% \def\rawcharacter#1{\getvalue{rchr:#1}}
this means that all chars are round tripped to themselves in output files!
raw characters are not active and they are therefore equivalent to \char
it's enough then to put
\def\numcharacter#1{\rawcharacter{#1}}%
\let\dochar\numcharacter
into cont-new.tex
(i will discuss this in more detail with taco later)
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Hans Hagen wrote:
Vit Zyka wrote:
Martin Kolařík wrote:
Hi Hans,
I've analyzed the situation using different combinations of regimes and
encodings, including switching off handling (\donothandleactivecharacter)
and it seems to me, that every text with chars 127, which is fully
expanded (as in 8bit.tex), must cause difficulties, because TOC entry read
back from TUO is scanned independently and thus spaces are gobbled.
Hi Martin,
we have discussed this problem a year ago. In that time I solve it just
writing '{}' in each title where was needed, like
\chapter{Dobré{} ráno}
Now I have cooked an automatic solution. It is not optimal (effective)
but working. The only needs is to redefine
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
and to load appropriate encoding file once more. Since it is banned a
new macro \reuseencoding was introduce:
For Hans:
It would be nice if this feature was enabled in a standard distro.
Perhaps you will find some more optimal solution...
---
\unprotected
\def\doreuseencoding#1%
{\letvalue{\c!file\f!encodingprefix#1}\empty
\makeshortfilename[\f!encodingprefix#1]%
\startreadingfile
\readsysfile\shortfilename
{\showmessage\m!encodings2{#1}}
{\showmessage\m!encodings3{#1}}%
\stopreadingfile}
\def\reuseencoding[#1]%
{\processcommalist[#1]\doreuseencoding}
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
\reuseencoding[ec]
\enableregime[latin2]
\starttext
\writetolist[chapter]{1}{Dobré ráno}
\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
\placecontent
\stoptext
the {} may break liguature building (and maybe kerning) ... taco knows ...
Hmmm, that's right.
I got a brainwave ...
\enableregime[latin2]
\starttext
\def\numcharacter#1{\rawcharacter{#1}}%
\let\dochar\numcharacter
So there is no need to have only 7-bit chars in tui/tuo etc.? All right,
I think this will be better also for sorting. Sounds promissing.
\writetolist[chapter]{1}{Dobré ráno}
\expanded{\writetolist[chapter]{2}{Dobré odpoledne}}
\placelist[chapter][criterium=text]
test
\typefile{test.tuo}
\stoptext
this can be sped up (a bit) with
% \dostepwiserecurse{0}{255}{1}
% {\setevalue{rchr:\recurselevel}{\rawcharacter\recurselevel}}
% \def\rawcharacter#1{\getvalue{rchr:#1}}
this means that all chars are round tripped to themselves in output files!
raw characters are not active and they are therefore equivalent to \char
it's enough then to put
\def\numcharacter#1{\rawcharacter{#1}}%
\let\dochar\numcharacter
into cont-new.tex
(i will discuss this in more detail with taco later)
All right, thanks Hans,
Vit
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Vit Zyka wrote: So there is no need to have only 7-bit chars in tui/tuo etc.? All right, I think this will be better also for sorting. Sounds promissing. if the regime is the same for a whole document ... indeed 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Hi Hans, the test file is attached, thanks, Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Hans Hagen Sent: Friday, March 31, 2006 7:01 PM To: [EMAIL PROTECTED]; mailing list for ConTeXt users Subject: Re: [NTG-context] Problem with encoding, XML and writetolist... Martin Kolařík wrote: Hi Hans, isn't there some news with the stuff? small test file needed to refresh my memory 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://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] Problem with encoding, XML and writetolist...
Martin Kolařík wrote: Hi Hans, the test file is attached, what input encoding is used here? i get the same chapter title as toc entry is your tex configured for 8 bit (natural.ctx) 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Aha, here maybe will be the solution :-) I'am using standalone Win32 distribution from Pragma and I'm running texexec with --translate=cp1252cs. Typescripts use il2, which corresponds to fonts, of course. If I run the code without XML (if I transcribe XML to \chapter etc.) I get toc entry correctly too. Where should I look for more? What is natural.ctx? Thank you, Martin -Original Message- From: Hans Hagen [mailto:[EMAIL PROTECTED] Sent: Monday, April 03, 2006 10:36 AM To: [EMAIL PROTECTED]; mailing list for ConTeXt users Subject: Re: [NTG-context] Problem with encoding, XML and writetolist... Martin Kolařík wrote: Hi Hans, the test file is attached, what input encoding is used here? i get the same chapter title as toc entry is your tex configured for 8 bit (natural.ctx) 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Martin Kolařík wrote: Aha, here maybe will be the solution :-) I'am using standalone Win32 distribution from Pragma and I'm running texexec with --translate=cp1252cs. Typescripts use il2, which corresponds to fonts, of course. If I run the code without XML (if I transcribe XML to \chapter etc.) I get toc entry correctly too. Where should I look for more? What is natural.ctx? this is a one-to-one translation vector, and the one standard used by context; forget about all those other mappings, they can be done using regimes; you can use an il2 input regime, and any (resonable) font encoding, 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Hans Hagen wrote: Martin Kolařík wrote: Aha, here maybe will be the solution :-) I'am using standalone Win32 distribution from Pragma and I'm running texexec with --translate=cp1252cs. Typescripts use il2, which corresponds to fonts, of course. If I run the code without XML (if I transcribe XML to \chapter etc.) I get toc entry correctly too. Where should I look for more? What is natural.ctx? this is a one-to-one translation vector, and the one standard used by context; forget about all those other mappings, they can be done using regimes; you can use an il2 input regime, and any (resonable) font encoding, Hans specifically for you: \mainlanguage[cz] \enableregime[windows] % or \enableregime[latin2] for il2 is enough for Latin Modern and Czech. Vit ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Thanks Vit, your solution perfectly works (I tried it :-); but not for me -- in
my case (and in another mine cases too) I use XML code, which remaps some
pieces to \chapter. And during the expansion accented characters are replaced
with \char xxx, this is written to tui/tuo file and read back without spaces
-- the spaces are gobbled by TeX's number syntactic rule...
But, Hans, when I added \mainlanguage[cz] before \enableregime[windows] in
8bit.tex and run texexec with --translate=cp1250cs, I got:
! Illegal parameter number in definition of \@@expanded.
to be read again
\crcr
\oalign [EMAIL PROTECTED] \lineskip .25ex\ialign {##\crcr
#1\crcr }}
\encircled ...\tx #1}}\hfil \crcr \mathhexbox 20D}
}
\XML:dat:title -Ä
luŁouŔcÝ koný ˙pÝ
\expanded ...\long \xdef \@@expanded {\noexpand #1
}\@@expanded
l.3 /chapter
Thank you,
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Vit Zyka
Sent: Monday, April 03, 2006 1:18 PM
To: mailing list for ConTeXt users
Subject: Re: [NTG-context] Problem with encoding, XML and writetolist...
Hans Hagen wrote:
Martin Kolařík wrote:
Aha, here maybe will be the solution :-)
I'am using standalone Win32 distribution from Pragma and I'm running texexec
with --translate=cp1252cs. Typescripts use il2, which corresponds to fonts,
of course. If I run the code without XML (if I transcribe XML to \chapter
etc.) I get toc entry correctly too.
Where should I look for more? What is natural.ctx?
this is a one-to-one translation vector, and the one standard used by
context; forget about all those other mappings, they can be done using
regimes; you can use an il2 input regime, and any (resonable) font encoding,
Hans
specifically for you:
\mainlanguage[cz]
\enableregime[windows] % or \enableregime[latin2] for il2
is enough for Latin Modern and Czech.
Vit
___
ntg-context mailing list
ntg-context@ntg.nl
http://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] Problem with encoding, XML and writetolist...
On 4/3/06, Martin Kolařík wrote: which is not good. And I am not able, when not using cp1250.tcx, recode win1250 (default for win) to latin2. There I am able to write regime for myself (cp1250), but I suppose, that whenever characters will not expand to \char XXX form, cp1250.tcx still will be working and usable. Hans, I would guess that more than 50% of Slavic Windows users (ie. Slovenian, Croatian, Chech, Slovak, ...) use the cp1250 encoding (including me). Would it be possible to add at least this file http://pub.mojca.org/tex/enco/contextbase/regi-cp1250.tex to the default ConTeXt distribution? (with synonyms windows-1250 and cp1250). This has probably nothing to do with the problem described here, but I believe that many users would appreciate to have that encoding (called regime in ConTeXt) available. when I added \mainlanguage[cz] before \enableregime[windows] in 8bit.tex and run texexec with --translate=cp1250cs, I got: \enableregime[windows] is cp1252 (Western European Windows) not cp1250 (Central European Windows), --translate=cp1250cs is cp1250 (supposing that you don't use \enableregime[windows], but the default one): everything will be mixed up if you use both simultaneously. If you download the file mentioned above (place it into the current directory or somewhere in the TeX tree and refresh the filename database) or if Hans adds it to the distribution, you can use \input regi-cp1250 \enableregime[cp1250] This probably won't solve your problem with missing spaces (didn't try it), but you'll have the proper encoding. Mojca ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Thanks Mojca, I downloaded your regime file; now I will not need write it myself :-) Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mojca Miklavec Sent: Monday, April 03, 2006 2:33 PM To: [EMAIL PROTECTED]; mailing list for ConTeXt users; Hans Hagen Subject: Re: [NTG-context] Problem with encoding, XML and writetolist... On 4/3/06, Martin Kolařík wrote: which is not good. And I am not able, when not using cp1250.tcx, recode win1250 (default for win) to latin2. There I am able to write regime for myself (cp1250), but I suppose, that whenever characters will not expand to \char XXX form, cp1250.tcx still will be working and usable. Hans, I would guess that more than 50% of Slavic Windows users (ie. Slovenian, Croatian, Chech, Slovak, ...) use the cp1250 encoding (including me). Would it be possible to add at least this file http://pub.mojca.org/tex/enco/contextbase/regi-cp1250.tex to the default ConTeXt distribution? (with synonyms windows-1250 and cp1250). This has probably nothing to do with the problem described here, but I believe that many users would appreciate to have that encoding (called regime in ConTeXt) available. when I added \mainlanguage[cz] before \enableregime[windows] in 8bit.tex and run texexec with --translate=cp1250cs, I got: \enableregime[windows] is cp1252 (Western European Windows) not cp1250 (Central European Windows), --translate=cp1250cs is cp1250 (supposing that you don't use \enableregime[windows], but the default one): everything will be mixed up if you use both simultaneously. If you download the file mentioned above (place it into the current directory or somewhere in the TeX tree and refresh the filename database) or if Hans adds it to the distribution, you can use \input regi-cp1250 \enableregime[cp1250] This probably won't solve your problem with missing spaces (didn't try it), but you'll have the proper encoding. Mojca ___ ntg-context mailing list ntg-context@ntg.nl http://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] Problem with encoding, XML and writetolist...
On 2/28/06, Martin Kolařík wrote:
Hi all,
I have problem with chars encoding now; I have updated ConTeXt sometimes in
January; before the time I was using old (year) version. In this
prehistorical version the problem was not present.
What is the stuff? The following code generates content with titles without
spaces -- accented characters are replaced with \char XXX variant, so during
reading TUI line TeX gobbles a space after XXX as a part of number syntax
rule.
Can I do something? With encoding? With XML?
Encoding has nothing to do with it. I don't really understand the
\[un]expanded commands in TeX, but this part could theoretically be
problematic:
{\expanded
{\section{\XMLflush{title
Consider the following (encoding-independent) minimal example, just in
case that this can help any of the gurus to understand the problem:
\defineXMLenvironment
[chapter]
{\defineXMLsave[title]}
{\expanded
{\section{\XMLflush{title
\starttext
\startbuffer
chapter
title$a+b$/title
/chapter
\stopbuffer
\processXMLbuffer
\placecontent[criterium=all]
\stoptext
The entry in TOC is different from the title (one is in math mode and
the other one writen with dollars - literally).
Mojca
Thank you very much, have a nice day, Martin
Code:
\defineXMLenvironment
[chapter]
{\defineXMLsave[title]}
{\expanded
{\chapter\XMLflush{title}}}
\starttext
\startbuffer
chapter
titleAhojá hojč kuna/title
/chapter
\stopbuffer
\processXMLbuffer
\completecontent[criterium=all]
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
OK, expansion is not encoding, but expansion in this place here is not a
problem (I suppose). The section head is good, but the TOC entry not. So the
inner expansion (or conversion or detokenization or so) around writetolist
is probably affected by something, what now I cannot handle.
And what is strange -- Hans did not reproduce the behaviour (as he wrote),
so I am asking a trying to find the problem on my side (or lucky thougth
:-)...
Thank for your ideas and help,
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Mojca Miklavec
Sent: Monday, April 03, 2006 4:25 PM
To: [EMAIL PROTECTED]; mailing list for ConTeXt users
Subject: Re: [NTG-context] Problem with encoding, XML and writetolist...
On 2/28/06, Martin Kolařík wrote:
Hi all,
I have problem with chars encoding now; I have updated ConTeXt sometimes
in
January; before the time I was using old (year) version. In this
prehistorical version the problem was not present.
What is the stuff? The following code generates content with titles
without
spaces -- accented characters are replaced with \char XXX variant, so
during
reading TUI line TeX gobbles a space after XXX as a part of number
syntax
rule.
Can I do something? With encoding? With XML?
Encoding has nothing to do with it. I don't really understand the
\[un]expanded commands in TeX, but this part could theoretically be
problematic:
{\expanded
{\section{\XMLflush{title
Consider the following (encoding-independent) minimal example, just in
case that this can help any of the gurus to understand the problem:
\defineXMLenvironment
[chapter]
{\defineXMLsave[title]}
{\expanded
{\section{\XMLflush{title
\starttext
\startbuffer
chapter
title$a+b$/title
/chapter
\stopbuffer
\processXMLbuffer
\placecontent[criterium=all]
\stoptext
The entry in TOC is different from the title (one is in math mode and
the other one writen with dollars - literally).
Mojca
Thank you very much, have a nice day, Martin
Code:
\defineXMLenvironment
[chapter]
{\defineXMLsave[title]}
{\expanded
{\chapter\XMLflush{title}}}
\starttext
\startbuffer
chapter
titleAhojá hojč kuna/title
/chapter
\stopbuffer
\processXMLbuffer
\completecontent[criterium=all]
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://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] Problem with encoding, XML and writetolist...
Hi Hans, isn't there some news with the stuff? Thank you and have a nice day, Martin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Kolařík Sent: Tuesday, February 28, 2006 10:33 AM To: mailing list for ConTeXt users Subject: Re: [NTG-context] Problem with encoding, XML and writetolist... Here the file with 8bit chars is, Martin -Original Message- From: Hans Hagen [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 28, 2006 10:16 AM To: [EMAIL PROTECTED]; mailing list for ConTeXt users Subject: Re: [NTG-context] Problem with encoding, XML and writetolist... � wrote: Hi all, I have problem with chars encoding now; I have updated ConTeXt sometimes in January; before the time I was using old (year) version. In this prehistorical version the problem was not present. What is the stuff? The following code generates content with titles without spaces -- accented characters are replaced with \char XXX variant, so during reading TUI line TeX gobbles a space after XXX as a part of number syntax rule. can you send me a zip with the test file so that the 8 bit chars are ok? 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
Martin Kolařík wrote: Hi Hans, isn't there some news with the stuff? small test file needed to refresh my memory 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problem with encoding, XML and writetolist...
� wrote: Hi all, I have problem with chars encoding now; I have updated ConTeXt sometimes in January; before the time I was using old (year) version. In this prehistorical version the problem was not present. What is the stuff? The following code generates content with titles without spaces -- accented characters are replaced with \char XXX variant, so during reading TUI line TeX gobbles a space after XXX as a part of number syntax rule. can you send me a zip with the test file so that the 8 bit chars are ok? 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Problem with encoding, XML and writetolist...
Hi all,
I have problem with chars encoding now; I have updated ConTeXt sometimes in
January; before the time I was using old (year) version. In this
prehistorical version the problem was not present.
What is the stuff? The following code generates content with titles without
spaces -- accented characters are replaced with \char XXX variant, so during
reading TUI line TeX gobbles a space after XXX as a part of number syntax
rule.
Can I do something? With encoding? With XML?
Thank you very much, have a nice day, Martin
Code:
\defineXMLenvironment
[chapter]
{\defineXMLsave[title]}
{\expanded
{\chapter\XMLflush{title}}}
\starttext
\startbuffer
chapter
titleAhojá hojč kuna/title
/chapter
\stopbuffer
\processXMLbuffer
\completecontent[criterium=all]
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Problem with encoding, XML and writetolist...
Hi Hans,
I have problem with chars encoding now; I have updated ConTeXt sometimes in
January; before the time I was using old (year) version. In this
prehistorical version the problem was not present.
What is the stuff? The following code generates content with titles without
spaces -- accented characters are replaced with \char XXX variant, so during
reading TUI line TeX gobbles a space after XXX as a part of number syntax
rule.
Can I do something? With encoding? With XML?
Thank you very much, have a nice day, Martin
Code:
\defineXMLenvironment
[chapter]
{\defineXMLsave[title]}
{\expanded
{\chapter\XMLflush{title}}}
\starttext
\startbuffer
chapter
titleAhojá hojč kuna/title
/chapter
\stopbuffer
\processXMLbuffer
\completecontent[criterium=all]
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
