Am 2005-07-23 um 00:20 schrieb Mojca Miklavec:
I'm still slighlty confused by the encoding files (texnansi, ec,...,
in one case iso-8859-7 is used). Does it mean that it is impossible
(or at least very complex or slow) to access more than 256 characters
from a single font at once?
TeX as an
Mojca Miklavec wrote:
I'm still slighlty confused by the encoding files (texnansi, ec,...,
in one case iso-8859-7 is used). Does it mean that it is impossible
(or at least very complex or slow) to access more than 256 characters
from a single font at once?
indeed and since it's related to
Mojca Miklavec wrote:
A1.) prepare the files to be used as a source of transformation from
any character set to utf and prepare a list of synonyms for
encodings
In my point of view, that should only be a fallback. We already have
Iconv in ruby and can, if we know that ISO-8859-2 is a
Christopher Creutzig wrote:
conv = Iconv.new(UTF-16, ISO-8859-2)
255.times { |i| puts lookup[conv.iconv(%c % i)] }
to get the whole list, assuming we've filled the lookup hash first.
an alternative is to use the tcx files but that is kind of messy
so we need a utf-8 hash (can be loaded from
Christopher Creutzig wrote:
We already have
Iconv in ruby and can, if we know that ISO-8859-2 is a single byte
coding system, simply say
conv = Iconv.new(UTF-16, ISO-8859-2)
255.times { |i| puts lookup[conv.iconv(%c % i)] }
to get the whole list, assuming we've filled the lookup hash
Hans Hagen wrote:
So why not mapping the characters to unicode first and defining the
mapping from unicode to \TeXcommand only once? regi-* files (at least
in the meaning they have now) could be prepared automatically by a
script, less error-prone and without the need to say Some more
Christopher Creutzig wrote:
Hans Hagen wrote:
So why not mapping the characters to unicode first and defining the
mapping from unicode to \TeXcommand only once? regi-* files (at least
in the meaning they have now) could be prepared automatically by a
script, less error-prone and without
Mojca Miklavec wrote:
Hans Hagen wrote:
Mojca Miklavec wrote:
(concerning eregi-* files: you can define filesynonyms so we need a list of
filesynonyms and regimesynonyms)
What do you mean by writing file synonyms? Where would it be used?
\definefilesynonym
Hans Hagen wrote:
Mojca Miklavec wrote:
regi-lat.tex is interesting, made just for typesetting Croatian :)
Perhaps I can add some stuff there too.
\defineactivetoken đ {\pseudoencodeddj}
\defineactivetoken Ð {\pseudoencodedDJ}
This should be \dstroke and \Dstroke.
ok, changed
Thank
Mojca Miklavec wrote:
\Dstroke has some problems anyway, at least in cmr (lmr?). The
stroke should be on the left, but it is on the right. I thought it was
just because \tt don't have that glyph, but also the roman version is
rendered extremely bad.
in case of doubt, you can discuss this
Mojca Miklavec wrote:
maybe a better name is regi-ce or just regi-1250
regi-ce is a bad name as there are 4 central european encodings
(IBM-853, ISO-8859-2, MacCE and Windows-1250) plus Croatian. 1250
alone is probably OK, but there's no hint in file name about which
encoding is meant
Hans Hagen wrote:
Mojca Miklavec wrote:
(concerning eregi-* files: you can define filesynonyms so we need a list of
filesynonyms and regimesynonyms)
What do you mean by writing file synonyms? Where would it be used?
\definefilesynonym [mojka] [mojca]
\definefilesynonym [moika]
Mojca Miklavec wrote:
regi-lat.tex is interesting, made just for typesetting Croatian :)
Perhaps I can add some stuff there too.
\defineactivetoken đ {\pseudoencodeddj}
\defineactivetoken Ð {\pseudoencodedDJ}
This should be \dstroke and \Dstroke.
ok, changed
Where did the hungarumlaut
Mojca Miklavec wrote:
I'm now attaching a file for support for windows-1250-encoded files.
One character is missing (I don't know what to write for non-breaking
space) and it's not extensively tested or proved for typos. So if
someone can drop an eye on it, I'll be glad.
maybe a better name
Am 2005-07-17 um 22:37 schrieb Hans Hagen:
there are
\showcharacters
\showaccents
BTW I finally created the wiki page Visual Debugging for all the
\show... commands; I guess there are even more than I listed there,
and some descriptions are still missing (had no time to try them all).
Henning Hraban Ramm wrote:
Am 2005-07-17 um 22:37 schrieb Hans Hagen:
there are
\showcharacters
\showaccents
BTW I finally created the wiki page Visual Debugging for all the
\show... commands; I guess there are even more than I listed there,
and some descriptions are still missing
On 7/17/05, Hans Hagen [EMAIL PROTECTED] wrote:
Mojca Miklavec wrote:
regi-lat.tex is interesting, made just for typesetting Croatian :)
Perhaps I can add some stuff there too.
\defineactivetoken đ {\pseudoencodeddj}
\defineactivetoken Ð {\pseudoencodedDJ}
This should be \dstroke and
Am 2005-07-14 um 21:13 schrieb Steffen Wolfrum:
But, why is the Vietnamese example with
\enableregime[utf]
linked under
vis = visciiVISCIIVietnamesevis = visciiVISCII
Vietnamese
and not accessable with
utfUTF-8Unicode ? (Same for cyrillic)
Is this just a wrong link,
Henning Hraban Ramm wrote:
You did read http://contextgarden.net/Encodings_and_Regimes and
linked pages, did you?
If you learn anything new, please add it to the wiki!
Thank you! It was probably me who copy-pasted some of the material
there from some thread, but when I looked at it once again,
Hi,
now and then I saw threads on this list dealing with specific
problems of using various languages with utf-8 input in ConTeXt
(processing with pdftex, NOT xetex).
I know there is \enableregime[utf]
but what else I needed that the output equals my utf-8 input?
Could some maybe give a
Am 2005-07-14 um 11:30 schrieb Steffen Wolfrum:
I know there is \enableregime[utf]
but what else I needed that the output equals my utf-8 input?
Could some maybe give a short and usable How-To on common examples:
Greek
Russian
an East European language
and an Asian language?
You did read
Hi Henning,
Zitat von Henning Hraban Ramm [EMAIL PROTECTED]:
Am 2005-07-14 um 11:30 schrieb Steffen Wolfrum:
I know there is \enableregime[utf]
but what else I needed that the output equals my utf-8 input?
Could some maybe give a short and usable How-To on common examples:
Greek
On 7/14/05, Steffen Wolfrum [EMAIL PROTECTED] wrote:
Well, yes, I wasn't interested in e.g. VISCII, but I read the info for UTF.
But as you wrote linked pages I became more curious and looked up also those
pages. Indeed, there is more:
But, why is the Vietnamese example with
Steffen Wolfrum wrote:
I know there is \enableregime[utf]
but what else I needed that the output equals my utf-8 input?
Could some maybe give a short and usable How-To on common examples:
Greek
Russian
an East European language
and an Asian language?
You did read
24 matches
Mail list logo
