My guess would be that your latex engine doesn't support non-ascii
encodings. IIUC xetex supports unicode, but I'm no texpert.
> You received this message because you are subscribed to the Google Groups "asciidoc" group.
> To post to this group, send email to asci...@googlegroups.com.
> To unsubscribe from this group, send email to asciidoc+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
This problem is in dblatex, asciidoc generates the docbook:
The small i with grave accent is unicode 0xed which is a legal xml ID character.
You need to ask on the dblatex ML.
Doing it manually is indeed a (laborious) workaround.
The problem with just dropping accented characters is that the
resulting id then may not be unique.
> PS: I publish this answer for the next time i will forget this workaround
> and get blocked because in french you often get accents in titles.
> You received this message because you are subscribed to the Google Groups
> "asciidoc" group.
> To view this discussion on the web visit
Yep, same issue when you manually create the id :/
I don't know if it would be possible to have an option in asciidoc
conversion like --no-accents-in-ids ? I guess the xhtml output removes
the accents also, as it is so bad looking in a web browser ?
I committed a patch that should work around the problem: If the 'ascii-ids'
attribute is defined then non-ascii characters are stripped from auto-generated IDs:
> On 07/11/11 23:05, Lex Trotman wrote:
>> On Tue, Nov 8, 2011 at 8:55 AM, Fabrice Flore-Thï¿œbault
>> <fabr...@gmail.com> wrote:
>> > So for the present, as tools used to convert docbook to pdf are not
>> > supporting accents in ids, there is this workaround to use accents in
>> > titles: manually redefine each title id by declaring it before the
>> > title:
>> > for example:
>> > [[this-is-an-id-for-my-title-without-accents]]
>> > === now i cï¿œn have a tï¿œtle with accï¿œnts
>> > A more pragmatic/automated approach could be to automatically remove
>> > accents
>> > in generated ids. (But i don't know how to achieve this)
>> Doing it manually is indeed a (laborious) workaround.
>> The problem with just dropping accented characters is that the
>> resulting id then may not be unique.
> Yep, same issue when you manually create the id :/
> I don't know if it would be possible to have an option in asciidoc conversion
> like --no-accents-in-ids ? I guess the xhtml output removes the accents also,
> as it is so bad looking in a web browser ?
Now that the 'ascii-ids' attribute has been added, we shouldn't stop
trying to get the tools to support accented characters.
I would hate to see this workaround block any progress in the tools. So,
please, Fabrice, do report and track those issues in the tools you use
as a courtesy to AsciiDoc ;-)
[Any errors in spelling, tact or fact are transmission errors]
Good suggestion, I've applied a patch to the trunk:
On 01/01/12 14:42, Simon wrote:
> Hi list!
> Here's a description of a method for a slightly better workaround:
> This way, accented letters such as ï¿½, ï¿½, ï¿½ will become a, o, i, making
> ids a bit more recognizable for some languages. Characters such as
> ï¿½ and ï¿½ will
> still get deleted, though.
> Happy New Year!
> /Simon Kï¿½gedal Reimer