Just to follow up, something really weird happens when using stylistic
sets 6 and 7: "dogstarman" becomes "doaaarrman". The two PDFs
demonstrate the difference between MiKTeX 2.8 and tl2010. Also see
http://gabriolan.ca/gabriola-font-variants/ for reference (MiKTeX
stumbles on ss06 and ss07, but no
I've been seeing something different altogether. In addition to
activating +calt by default, it also gives some strange output when
using stylistic sets in Gabriola. I've attached 2 images:
tl2010gabriola shows the behaviour with tl2010 (I just installed
today), miktex28gabriola shows the correct o
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)
On Oct 17, 2010, at 12:40 AM, Will Robertson wrote:
> On 2010-10-17 02:17:37 +1030, Herbert Schulz said:
>
>> On Oct 16, 2010, at 10:31 AM, enrico.grego...@univr.it wrote:
>>> \expandafter\let\csname intexpr_if_even:nTF\expandafter\endcsname
>>> \csname int_if_even:nTF\endcsname
>> That certain
Am 17.10.2010 um 11:27 schrieb Roland Kuhn:
>
> On Oct 17, 2010, at 11:04 , Philipp Stephani wrote:
>
>>
>> Am 17.10.2010 um 08:25 schrieb Roland Kuhn:
>>
>>>
>>> On Oct 17, 2010, at 00:53 , Herbert Schulz wrote:
>>>
On Oct 16, 2010, at 5:11 PM, Roland Kuhn wrote:
> I w
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
Hi Will,
Do not worry about it. These things do happen and all is work in
progress.
Also, it it was that easy we would not need you, and appreciate your
hard work so much!!
regards
Keith.
Am 17.10.2010 um 07:40 schrieb Will Robertson:
>
> Well, we try
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 11:04 , Philipp Stephani wrote:
>
> Am 17.10.2010 um 08:25 schrieb Roland Kuhn:
>
>>
>> On Oct 17, 2010, at 00:53 , Herbert Schulz wrote:
>>
>>>
>>> On Oct 16, 2010, at 5:11 PM, Roland Kuhn wrote:
>>>
I wanted to try out different approaches to the french hyphenatio
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
Le 17/10/2010 11:10, Ulrike Fischer a écrit :
Am Sat, 16 Oct 2010 16:24:44 +0200 schrieb Wolfgang Schuster:
Would this replace every occurence of "im" in the input? Including
the "im" in \scratchdimen, the "im" in the second 1im and the "im"
in immens?
Yes. This is why I said that the solutio
Am Sat, 16 Oct 2010 16:24:44 +0200 schrieb Wolfgang Schuster:
>>> Would this replace every occurence of "im" in the input? Including
>>> the "im" in \scratchdimen, the "im" in the second 1im and the "im"
>>> in immens?
>>
>> Yes. This is why I said that the solution cannot work out-of-the-box
>>
Am 17.10.2010 um 08:25 schrieb Roland Kuhn:
>
> On Oct 17, 2010, at 00:53 , Herbert Schulz wrote:
>
>>
>> On Oct 16, 2010, at 5:11 PM, Roland Kuhn wrote:
>>
>>> I wanted to try out different approaches to the french hyphenation problem
>>> involving apostrophes, thereby including
>>>
>>> \u
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
22 matches
Mail list logo
