On Oct 21, 2010, at 20:53, Arthur Reutenauer
wrote:
> Actually, it's both. U+2019 is really supposed to be used as a "curly"
> apostrophe as well as a closing quotation mark. The name is RIGHT SINGLE
> QUOTATION MARK, by the way.
And instead of "closing," I really should have written "on
> There were no quotation marks in this part of the
> test, Mojca; the symbol at which you were looking
> was an apostrophe.
Actually, it's both. U+2019 is really supposed to be used as a "curly"
apostrophe as well as a closing quotation mark. The name is RIGHT SINGLE
QUOTATION MARK, by the
Mojca Miklavec wrote:
Mind that you don't even care to write your name properly. You write
(Webmaster, Ret'd)
instead of using the proper
(Webmaster, Ret’d)
with single quotation mark. You don't care to use “proper quotation
marks” in the text you type.
There were no quotation mark
Mojca Miklavec wrote:
> Can we please close this off-topic discussion and solve the problem
> with \savinghyphcodes instead?
(answered off-list)
** Phil.
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/x
On Thu, Oct 21, 2010 at 17:45, Philip Taylor (Webmaster, Ret'd) wrote:
>
> Barry MacKichan wrote:
>>
>> Weren't these called 'code pages'?
>
> Not unless you know something I don't, Barry
> (which is more than probable !).
>
> A document written in code page X could not
> be differentiated from a d
Peter Dyballa wrote:
Then some characters would have hundreds (in future thousands) of code
pages... (I then would love Unicode.)
No, each character would have exactly one code page.
For example (and omitting any unnecessary distinctions)
the English letter "d" would be in the English code
Am 21.10.2010 um 17:45 schrieb Philip Taylor (Webmaster, Ret'd):
A document written in code page X could not
be differentiated from a document written in
code page Y as far as I know, whereas in my
putative "Omni-code [tm]" the code page would
be implicit in the encoding of each character.
T
Barry MacKichan wrote:
Weren't these called 'code pages'?
Not unless you know something I don't, Barry
(which is more than probable !).
A document written in code page X could not
be differentiated from a document written in
code page Y as far as I know, whereas in my
putative "Omni-code [tm
Weren't these called 'code pages'?
--Barry
On 10/21/10 4:29 AM, Philip Taylor (Webmaster, Ret'd) wrote:
Tobias Schoel wrote:
That's difficult, because languages and scripture are evolving. Is there
a difference between Montenegrin and Serbian? Will there be a difference
for German German an
Tobias Schoel wrote:
That's difficult, because languages and scripture are evolving. Is there
a difference between Montenegrin and Serbian? Will there be a difference
for German German and Swiss German (the standardardizations of both
languages are nearly identical, but there is an important t
Am 20.10.2010 10:44, schrieb Philip Taylor (Webmaster, Ret'd):
[1] IMVVVHO, a successor to Unicode should have one plane per
written language (and perhaps even per dialect thereof), so
that a document written using this encoding will automatically
carry the appropriate language semantics without
On Wed, Oct 20, 2010 at 09:44:36AM +0100, Philip Taylor (Webmaster, Ret'd)
wrote:
>
>
> Khaled Hosny wrote:
>
> >Unicode is full of "compatibility with legacy encodings" non-sense, IMO
> >it should just be ignored. AFAIK, comma forms were added in Unicode
> >3.0.0 and that more than 10 years no
Khaled Hosny wrote:
Unicode is full of "compatibility with legacy encodings" non-sense, IMO
it should just be ignored. AFAIK, comma forms were added in Unicode
3.0.0 and that more than 10 years now, if we continue to support the old
broken practice it will never vanish.
Nor will it vanish ju
On Wed, Oct 20, 2010 at 08:47:32AM +0100, Philip Taylor (Webmaster, Ret'd)
wrote:
>
>
> Khaled Hosny wrote:
>
> >On Wed, Oct 20, 2010 at 12:21:12AM +0200, Mojca Miklavec wrote:
>
> >>Arthur also reminded me that one might want to treat scedilla and
> >>scommaaccent as equivalent characters for
Khaled Hosny wrote:
On Wed, Oct 20, 2010 at 12:21:12AM +0200, Mojca Miklavec wrote:
Arthur also reminded me that one might want to treat scedilla and
scommaaccent as equivalent characters for Romanian,
Lately, I've been told that Romanians are now strongly against this
scedilla=scommaacc
On Wed, Oct 20, 2010 at 00:31, Khaled Hosny wrote:
> On Wed, Oct 20, 2010 at 12:21:12AM +0200, Mojca Miklavec wrote:
>> Arthur also reminded me that one might want to treat scedilla and
>> scommaaccent as equivalent characters for Romanian,
>
> Lately, I've been told that Romanians are now strongly
On Wed, Oct 20, 2010 at 12:21:12AM +0200, Mojca Miklavec wrote:
> Arthur also reminded me that one might want to treat scedilla and
> scommaaccent as equivalent characters for Romanian,
Lately, I've been told that Romanians are now strongly against this
scedilla=scommaaccent thing being legacy art
On Mon, Oct 18, 2010 at 22:36, wrote:
>> Would \savinghyphcodes help? According to the documentation of
>> e-TeX, setting this parameter to a positive value would save the
>> \lccodevalues in effect during the execution of \patterns and e-TeX (so also
>> XeTeX and LuaTeX) would use those "frozen"
> Would \savinghyphcodes help? According to the documentation of
> e-TeX, setting this parameter to a positive value would save the
> \lccodevalues in effect during the execution of \patterns and e-TeX (so also
> XeTeX and LuaTeX) would use those "frozen" values for hyphenation
> purposes.
I add
On Mon, Oct 18, 2010 at 12:10:32AM +0200, Peter Dyballa wrote:
> They're presumingly pdfTeX users.
No. Many users still use the ASCII quote in their documents (U+0027).
I see examples of that all the time, for instance (but it's really only
one example, among many others), in the e-mail I'm rep
Am 17.10.2010 um 23:34 schrieb Arthur Reutenauer:
But the overwhelming majority of users still type in the ASCII quote
sign and this situation has to be taken in account
They're presumingly pdfTeX users. With LuaTeX and XeTeX, and that's
probably the target of UTF-8 based hyphenation files
Arthur Reutenauer wrote:
On the other hand, why not do it right? "0027 is some ASCII
single-high-vertical-short-line which was used in the middle-ages of text input to
mean apostrophe, single quotation mark, prime, etc. Now that we have gone way past
the french revolution (pun intended), wh
> On the other hand, why not do it right? "0027 is some ASCII
> single-high-vertical-short-line which was used in the middle-ages of text
> input to mean apostrophe, single quotation mark, prime, etc. Now that we have
> gone way past the french revolution (pun intended), why not enter those
> c
> Would setting
>
> \lccode "2019 = "27
>
> be any help?
Yes, that one line of code... But as you say, it has side effects as
well, which is why we didn't adopt it in hyph-utf8.
Arthur
--
Subscriptions, Archive, and List information,
> I'm in a rush now, so I cannot answer in too much extent, but what you
> observe is a "known problem that needs a nice idea to solve it" (or we
> can simply create and load another bunch of patterns) and it's present
> in both XeTeX and LuaTeX (only that it's mapped to quotation mark in
> LuaTeX)
Am 17.10.2010 um 11:22 schrieb Roland Kuhn:
Well, konsole can do that, too, but all of them (AFAIK) put each
nice and variable-width glyph at their assumed monospace location,
which is the worst possible solution to my mind (and eyes).
GNU Emacs has an ANSI compliant terminal emulation. Mo
On Oct 17, 2010, at 11:29 , Cyril Niklaus wrote:
>> On 17 oct. 2010, at 17:09, Roland Kuhn wrote:
>>
>>> On Oct 16, 2010, at 15:21 , Cyril Niklaus wrote:
>>> In the meantime, the "solution" I used was to change fonts…
>>>
>> That basically disables hyphenation for this word, like would \/.
> I
Le 17/10/2010 11:29, Cyril Niklaus a écrit :
In the meantime, the "solution" I used was to change fonts…
That basically disables hyphenation for this word, like would \/.
I noticed that if I wrote l'in\-formation, it would then hyphenate at the
suggested point and not after the apostrophe.
> On 17 oct. 2010, at 17:09, Roland Kuhn wrote:
>
>> On Oct 16, 2010, at 15:21 , Cyril Niklaus wrote:
>
>>> On 16 oct. 2010, at 20:57, Jonathan Kew wrote:
>>>
>>> Would setting
>>>
>>> \lccode "2019 = "27
>>>
>>> be any help?
>> I do have it in the document preamble, to no effect (with straigh
On Oct 17, 2010, at 10:48 , Peter Dyballa wrote:
> Am 17.10.2010 um 10:09 schrieb Roland Kuhn:
>
>> BTW: does anyone know a “terminal” which can use proportional fonts? That
>> would be a nice compromise between Turing-complete language and
>> intra-paragraph-WYSIWYG (I’m sorry to say that I’m
Am 17.10.2010 um 10:09 schrieb Roland Kuhn:
BTW: does anyone know a “terminal” which can use proportional fonts?
That would be a nice compromise between Turing-complete language and
intra-paragraph-WYSIWYG (I’m sorry to say that I’m basically married
to vim).
Xterm, uxterm, ...
--
Mit
On Oct 16, 2010, at 15:21 , Cyril Niklaus wrote:
> On 16 oct. 2010, at 19:44, enrico.grego...@univr.it wrote:
>
>> It's quite subtle, I believe. There are no patterns containing U+2019 (RIGHT
>> SINGLE QUOTATION MARK), into which each apostrophe is changed by
>> tex-text.map; so the pattern "1inf
On 16 oct. 2010, at 19:12, Paul Isambert wrote:
>
> That's absolutely normal, that's even the reason why we use TeX :)
> TeX builds a paragraph as a whole; if you remove some words at the end of
> your paragraph, it might change its entire shape.
I sorta knew that at a certain point in time… but
On 16 Oct 2010, at 12:42, Mojca Miklavec wrote:
> On Sat, Oct 16, 2010 at 11:47, Cyril Niklaus wrote:
>> Hello all,
>> I'd never had (or noticed) that problem before, so I don't know if it's a
>> new thing or something I do that does not comply. The problem is simple,
>> hyphenation occurs betwe
On Sat, Oct 16, 2010 at 11:47, Cyril Niklaus wrote:
> Hello all,
> I'd never had (or noticed) that problem before, so I don't know if it's a new
> thing or something I do that does not comply. The problem is simple,
> hyphenation occurs between an apostrophe and the word it follows :
> l'informa
> Hello all,
> I'd never had (or noticed) that problem before, so I don't know
> if it's a new thing or something I do that does not comply. The
> problem is simple, hyphenation occurs between an apostrophe and
> the word it follows : l'information in my case becomes l'-information.
> I'm using
I can't answer your main question (about hyphenation after an
apostrophe), but there are some points I can explain.
Le 16/10/2010 11:47, Cyril Niklaus a écrit :
In making the small version I include here, I also noticed something
surprising: the hyphenation changed depending on the length of
Hello all,
I'd never had (or noticed) that problem before, so I don't know if it's a new
thing or something I do that does not comply. The problem is simple,
hyphenation occurs between an apostrophe and the word it follows :
l'information in my case becomes l'-information.
I'm using the latest u
38 matches
Mail list logo
