Am Sat, 04 Jun 2011 11:26:37 +0200 schrieb Taco Hoekwater:
>> Thank you everybody for your answers. Writing Tr{\"a}ger as Thomas
>> suggested works well, but unfortunately, I'm using Mendeley Desktop
>> for the management of my bibtex file and I can't seem to be able to
>> influen
> I was actually thinking of precomposed vs. combining diacritics. I was
> blissfully unaware of the non-shortest-form problem up until now...
Ah, OK. But that's exactly the issue for which canonical equivalence
was designed, and in a Unicode-aware version of BibTeX that shouldn't be
an issue.
On Mon 06 Jun 2011, Arthur Reutenauer wrote:
> > Well, there *is* more than one way to represent ä in UTF-8
>
> If you mean "non-shortest" forms such as 0xE0 0x83 0xA4 or 0xF0 0x80
> 0x83 0xA4, then no, they have been forbidden since Unicode 3 in 2000
> (formally Corrigendum #1, see
> http://www.
> Well, there *is* more than one way to represent ä in UTF-8
If you mean "non-shortest" forms such as 0xE0 0x83 0xA4 or 0xF0 0x80 0x83
0xA4, then no, they have been forbidden since Unicode 3 in 2000 (formally
Corrigendum #1, see http://www.unicode.org/versions/corrigendum1.html).
Arthur
I think I'll go for the piping option then, which seems to be the easiest
way out.
Thanks for the insights, I didn't actually know much about the interplay of
context and bibtex until this little problem occured to me...
Julian
2011/6/4 Pontus Lurcock
> On Sat 04 Jun 2011, Julian Becker wrote
On Sat 04 Jun 2011, Julian Becker wrote:
> I'm not familiar with the intricacies and details of UTF8 encoding,
> but is it possible that there is a byte missing from the "ä" which
> has been cut off during the abbreviation process?
Well, there *is* more than one way to represent ä in UTF-8, but i
On 06/04/2011 11:23 AM, Julian Becker wrote:
Thank you everybody for your answers. Writing Tr{\"a}ger as Thomas
suggested works well, but unfortunately, I'm using Mendeley Desktop
for the management of my bibtex file and I can't seem to be able to
influence the way in which it e
I can also add that in the first case with the author name "Träger", the
generated bbl-file looks messed up and (Notepad++ doesn't recognize the
encoding as UTF8. Changing the encoding to UTF8 manually shows the complete
names "Träger" correctly, but the abbreviations (what should have been
"Trä06"
Thank you everybody for your answers. Writing Tr{\"a}ger as Thomas
suggested works well, but unfortunately, I'm using Mendeley Desktop for the
management of my bibtex file and I can't seem to be able to influence the
way in which it encodes the special characters.
@Mojca: Indeed, it also fails if
On Fri 03 Jun 2011, Thomas A. Schmitz wrote:
> But I admit it's not easy to know that, bibtex documentation is a
> real mess
Patience please! ‘This document will be expanded when BibTEX version
1.00 comes out’ -- BIBTEXing, February 8, 1988.
:-)
Pont
On Jun 3, 2011, at 8:38 PM, Julian Becker wrote:
> I came across an issue in context (context ver. 2011.05.18 22:26, LuaTeX ver:
> beta-0.65.0-2010121421 (rev 4034) ) when trying to cite a bibliography item
> having an author with a German umlaut "ä"
>
>From btxdoc, which is part of texlive:
I came across an issue in context (context ver. 2011.05.18 22:26, LuaTeX
ver: beta-0.65.0-2010121421 (rev 4034) ) when trying to cite a bibliography
item having an author with a German umlaut "ä"
Compiling the short example below, produces the following output and then
12 matches
Mail list logo
