On Sat, Apr 3, 2010 at 6:49 PM, Hans Hagen
On 3-4-2010 6:44, Wolfgang Schuster wrote:
Am 03.04.10 17:11, schrieb luigi scarso:
You said encodings are gone in mkiv but this isn't true,
id est ?
\enableregime[latin1] \starttext AOUÄÖÜ \stoptext
acceptable in mkii horror in mkiv
When encodins are really gone this should fail with mkiv but what you get as output is 'AOUÄÖU' what means encodings aren't gone. It's recommended to use UTF-8 encoded input but there is nothing which prevents you from using another one.
or invent one by myself too --why not ?
indeed and there is no reason to drop backward compatibility in that respect yes yes , of course backward comp. But, apart this (which is important etc etc etc) any other issue ? I mean: I'm typesetting international pricelist from 7 years, it would be impossible to manage thing without unicode and context. If one submit a file in a known (iconv --list) encoding I convert it in unicode utf *before* and then process with mkiv. And iconv can be eventually link in lua, by a dynamic linking --- not need for peek and poke sources. Or it can be done in pure lua. Am I wrong ? Anyway I do the rules --- only one input encoding: unicode utf-8 . Sorry for the others.
of course font (and math) encodings are completely gone unicode input & uncode fonts are the news --- you typeset what you see I understand that ``correct'' is the right way but please “correct” is better (the perfect way) (I mean U+201C LEFT DOUBLE QUOTATION MARK correct U+201D RIGHT DOUBLE QUOTATION MARK ) -- luigi