Am 13.11.2011 um 23:14 schrieb Ross Moore:
> Is there a EUR 0,01 coin? :-)
Yes, 1 ¢ and 2 ¢ coins exist.
--
Mit friedvollen Grüßen
Pete
When Richard Stallman goes to the loo, he core dumps.
--
Subscriptions, Archive, and List information
Hi all,
On 14/11/2011, at 7:55 AM, Zdenek Wagner wrote:
> Before typing a document one should think what will be the purpose of
> it. If the only purpose is to have it typeset by (La)TeX, I would just
> use well known macros and control symbols (~, $, &, %, ^, _). If the
> text should be stored i
2011/11/13 Philip TAYLOR :
>
>
> Tobias Schoel wrote:
>>
>> Now, that the practicability is cleared, let's come back to the
>> philosophical part:
>
> Actually, I think this is the practical/pragmatic part,
> but let's carry on none the less ...
>>
>> Should =u00a0 be active and treated as ~ by de
Tobias Schoel wrote:
Now, that the practicability is cleared, let's come back to the
philosophical part:
Actually, I think this is the practical/pragmatic part,
but let's carry on none the less ...
Should =u00a0 be active and treated as ~ by default? Just like
u202f and u2009 should be act
Now, that the practicability is cleared, let's come back to the
philosophical part:
Should =u00a0 be active and treated as ~ by default? Just like
u202f and u2009 should be active and treated as \, and \,\hspace{0pt}?
Where would such a default take place:
- XeTeX engine
- XeLaTeX format
- s
On 11/13/2011 11:09 AM, Tobias Schoel wrote:
How much text flow control mechanism should be done by none-ASCII
characters? Unicode has different codepoints for signs with the same
meaning but different text flow control (space vs. non-break space). So
text flow could be controled via Unicode code
Am 13.11.2011 20:25, schrieb Zdenek Wagner:
2011/11/13 Tobias Schoel:
Am 13.11.2011 12:35, schrieb Zdenek Wagner:
2011/11/13:
On Sun, 13 Nov 2011, Petr Tomasek wrote:
make ~ not active when writing my own macros because it contradicts
the Unicode standard...)
Isn't it just as much a
2011/11/13 Tobias Schoel :
>
>
> Am 13.11.2011 12:35, schrieb Zdenek Wagner:
>>
>> 2011/11/13:
>>>
>>> On Sun, 13 Nov 2011, Petr Tomasek wrote:
make ~ not active when writing my own macros because it contradicts
the Unicode standard...)
>>>
>>> Isn't it just as much a "contradiction"
One option would be to colour-code them, but I was
more interested in the philosophy than the implementation.
** Phil.
Not in every case. How would you visually differentiate between all the
white space characters (space vs. non-break space, thin space (u2009)
vs. narrow no-break space
Am 13.11.2011 18:16, schrieb Philip TAYLOR:
Tobias Schoel wrote:
One opinion says, that using (La)TeX is programming. Consequently, each
character used should be visually well distinguishable. This is not the
case with all the Unicode white space characters.
Is that not a function of the
Tobias Schoel wrote:
One opinion says, that using (La)TeX is programming. Consequently, each
character used should be visually well distinguishable. This is not the
case with all the Unicode white space characters.
Is that not a function of the editor used ? Is it not valid
for an editor to
Am 13.11.2011 12:35, schrieb Zdenek Wagner:
2011/11/13:
On Sun, 13 Nov 2011, Petr Tomasek wrote:
make ~ not active when writing my own macros because it contradicts
the Unicode standard...)
Isn't it just as much a "contradiction" of the "standard" for \ to do
what \ does? I don't think tha
2011/11/13 :
> On Sun, 13 Nov 2011, Petr Tomasek wrote:
>> make ~ not active when writing my own macros because it contradicts
>> the Unicode standard...)
>
> Isn't it just as much a "contradiction" of the "standard" for \ to do
> what \ does? I don't think that is a good way to decide what TeX's
On Sun, 13 Nov 2011, Petr Tomasek wrote:
> make ~ not active when writing my own macros because it contradicts
> the Unicode standard...)
Isn't it just as much a "contradiction" of the "standard" for \ to do
what \ does? I don't think that is a good way to decide what TeX's
input format should be
14 matches
Mail list logo
