Wolfgang Schuster wrote:
Am 03.04.10 16:16, schrieb luigi scarso:
name space to avoid macro collision
Possible with internal commands but you can run into problems with
the user commands, a problem is also how LaTeX handle environments
For \begin{env} LaTeX expects a macro with the
@Taco
I think the current latex module does
\def\begin#1{\csname start#1\endcsname}
\def\end#1{\csname stop#1\endcsname}
but that all depends on how much latex compatibility is
really needed.
Only for latex/base/*
@Wolfgang
Most input encodings are supported in mkiv, only a few (e.g. cyr
Am 03.04.10 16:55, schrieb luigi scarso:
I care only unicode utf-8
This wasn't the question ;)
??
You said encodings are gone in mkiv but this isn't true,
ehat you use or what's the preferred encoding is another topic.
Wolfgang
On Sat, Apr 3, 2010 at 5:04 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
You said encodings are gone in mkiv but this isn't true,
id est ?
--
luigi
___
If your question is of interest to others as
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
When encodins are really gone this should fail with mkiv
but what you get as output is 'AOUÄÖU' what means encodings
aren't
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
When encodins are really gone this should fail with mkiv
but what you get as output is
On Sat, Apr 3, 2010 at 6:49 PM, Hans Hagen pra...@wxs.nl wrote:
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
On 3-4-2010 7:09, luigi scarso wrote:
but there is nothing which prevents you from using another one.
or invent one by myself too --why not ?
ah .. woul dhav emade a nice april 1 joke ... you announcing that there
would finally be a proper input as well as font encoding for italian!
Hans
On Sat, Apr 3, 2010 at 7:15 PM, Hans Hagen pra...@wxs.nl wrote:
ah .. woul dhav emade a nice april 1 joke ... you announcing that there
would finally be a proper input as well as font encoding for italian!
Uh? who needs them ?
never had a problem with italian context
--
luigi
me neither. Should I ? :)
-a-
On Apr 3, 2010, at 7:19 PM, luigi scarso wrote:
On Sat, Apr 3, 2010 at 7:15 PM, Hans Hagen pra...@wxs.nl wrote:
ah .. woul dhav emade a nice april 1 joke ... you announcing that
there
would finally be a proper input as well as font encoding for italian!
Uh?
On 3-4-2010 7:19, luigi scarso wrote:
On Sat, Apr 3, 2010 at 7:15 PM, Hans Hagenpra...@wxs.nl wrote:
ah .. woul dhav emade a nice april 1 joke ... you announcing that there
would finally be a proper input as well as font encoding for italian!
Uh? who needs them ?
never had a problem with
2010/4/3 Hans Hagen pra...@wxs.nl:
ah .. woul dhav emade a nice april 1 joke ... you announcing that there
would finally be a proper input as well as font encoding for italian!
After that can we have ascii please?
Best
Martin
Martin Schröder wrote:
2010/4/3 Hans Hagen pra...@wxs.nl:
ah .. woul dhav emade a nice april 1 joke ... you announcing that there
would finally be a proper input as well as font encoding for italian!
After that can we have ascii please?
ebcdic!
2010/4/3 Taco Hoekwater t...@elvenkind.com:
ebcdic!
UTF-EBCDIC?
UTF-5?
Best
Martin
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
14 matches
Mail list logo
