From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Error while compiling : ! String contains an invalid utf-8 sequence.
Date: Wed, 07 Dec 2011 18:45:52 +0100 [thread overview]
Message-ID: <4EDFA650.5040402@wxs.nl> (raw)
In-Reply-To: <CAA5sP+8uEMRQOHWr8NfrfSsCDsocF7qD5kc8pbnZiF3K5ziB-g@mail.gmail.com>
On 7-12-2011 17:37, Alexandre Krispin wrote:
> Thank you for your answer !
>
> Finally I am back to Latex until this problem is fixed. Though I have no
> knowledge about it, it seemed to me that the problem I got was more related
> to hanzi script than to bibtex, since the final problem of misplaced dots I
> had appeared only with hanzi script.
>
> Hans Hagen did not replied to it. That's why I suppose that one day if this
> problem related to hanzi script becomes a problem of general interest,
> maybe it will be fixed...
As mentioned on this list using a unicode (utf) engine with bibtex is
somewhat tricky. Interesting is that a similar problem occurred with
url's: bibtex has hard coded line lengths and if I'm right there has
been a fix that made lines wrap on spaces. However that does not help
with scripts that have no spaces. Somewhat strange is that bibtex was
not made compliant to other tex related programs in the sense that one
can configure the line length (which we would then set to 1000 or so).
In spite of repeated announcements of bibtex 1.0 (which would probably
not fix this issue anyway) it looks like the program is deep frozen.
Unfortunately it also has frozen some conventions that make it hard to
replace it.
Fixing it is probably something that an able programmer can do while
watching a movie at the same time were it not that touching bibtex seems
to be some kind of sacrilege.
I can imagine that someone makes a copy of bibtex, say ctxbibtex,
patches it to accept long lines and that we ship that one with context.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-12-07 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 18:50 Alexandre Krispin
2011-11-25 19:03 ` Christian
2011-11-25 20:09 ` Hans Hagen
2011-11-25 22:13 ` Alexandre Krispin
2011-11-25 23:56 ` Alexandre Krispin
2011-11-27 13:33 ` Mojca Miklavec
2011-11-27 16:13 ` Alexandre Krispin
2011-11-28 9:20 ` Wolfgang Schuster
2011-12-07 8:28 ` Thomas A. Schmitz
2011-12-07 16:37 ` Alexandre Krispin
2011-12-07 17:45 ` Hans Hagen [this message]
2011-11-26 9:35 ` Ulrike Fischer
2011-11-26 10:44 ` Alexandre Krispin
2011-11-26 11:39 ` Wolfgang Schuster
2011-11-26 11:41 ` Alexandre Krispin
[not found] <mailman.901.1322405047.4232.ntg-context@ntg.nl>
2011-11-28 7:08 ` S Barmeier
2011-11-28 8:42 ` Alexandre Krispin
2011-11-30 12:25 ` Alexandre Krispin
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=4EDFA650.5040402@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).