From: Hans Hagen <pragma@wxs.nl>
Subject: Re: bug in beta: extra \else
Date: Mon, 16 Oct 2006 19:16:54 +0200 [thread overview]
Message-ID: <4533BE86.7050803@wxs.nl> (raw)
In-Reply-To: <Pine.WNT.4.63.0610161056470.2748@nqvgln>
Aditya Mahajan wrote:
> On Sun, 15 Oct 2006, Vit Zyka wrote:
>
>> Great, thank you Hans!
>>
>> Let us process to teh next two problems also visible in the test file.
>>
>> 1. [snip]
>>
>
>
>> 2. Accented characters inside \typebuffer are type set as
>> \dochar {225}
>>
>
> This seems to be a bug. In utf-8 encoding, if an accented character is
> the first character of a buffer, it gets typed correctly. All other
> accented charaters come out as \dochar {225}. \getbuffer works fine.
>
> Can TeX choose the input encoding while writing files? If not, there
> may be really no robust way to solve this problem.
>
a solution if to completely move to utf-8 internally and then make chars > 127 unexpandable ; the problem is that whatever input encoding does not mix well with multipass utf data then
in mkiv we will follow a different route since luatex is utf internally
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-10-16 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 22:05 Vit Zyka
2006-10-11 7:47 ` Hans Hagen
2006-10-11 10:42 ` Vit Zyka
2006-10-11 19:40 ` Hans Hagen
2006-10-13 21:45 ` Vit Zyka
2006-10-13 23:16 ` Aditya Mahajan
2006-10-14 15:35 ` Wolfgang Schuster
2006-10-14 17:58 ` Hans Hagen
2006-10-15 21:59 ` Vit Zyka
2006-10-16 15:06 ` Aditya Mahajan
2006-10-16 15:09 ` Aditya Mahajan
2006-10-16 17:12 ` Hans Hagen
2006-10-18 11:02 ` Vit Zyka
2006-10-16 17:16 ` Hans Hagen [this message]
2006-10-16 19:51 ` Hans Hagen
2006-10-18 11:02 ` Vit Zyka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4533BE86.7050803@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).