On 15-3-2010 14:53, Mojca Miklavec wrote:
By the way, XeTeX also breaks, but in a different way. "Računalne
mreže" becomes "RaÄ“unalne mreže". Same option also doesn't do
anything.

MkIV works nicely, and I know I should probably be using that, but
LaTeX with hyperref can do unicode bookmarks in both XeTeX and pdfTeX,
so it would be really cool if ConTeXt would be able to do it as well.

Hm, i wonder what goes wrong, so can you make a test file? I was under the
impression that context could do it before latex if only because it was used
to test the<>  entries when that feature was added to pdftex so maybe
soemthing got lost (it might also be that some ecodings work better than
others, so let's assume utf)

I figured out that loading "\input spec-tst.mkii" before
\setupinteraction[state=start] works as expected in MKII (but then -
the backward compatibility is broken as well since one would have to
load the "tex" version of that file in past). Loading it after doesn't
have any influence.

It would be really nice if there was some more elegant way to use
UTF-8 in bookmarks than \input spec-tst.mkii.

i'll merge the tst code into the other spec files

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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

Reply via email to