#13 Accented characters not all rendered correctly

open
None
5
2005-09-28
2005-09-28
Maxim
No

When I enter the ë character in a .wyn document, I do
not see it in the PDF afterwards. The é character on
the other hand, IS rendered correctly.

I tried both to enter a ë directly and to put \"{e} in
my notes, but neither works. It turns out that n the
.tex file, the ë is converted to \''{e} (that two '
instead of one ") so it produces something different
from a ë character.

This also applies to Ó, I think. The ó character works
correctly, but Ó (capital) does not. é works fine too.
I haven't tested ö, ŕ and others.

Discussion

  • karlabbott

    karlabbott - 2005-09-28

    Logged In: YES
    user_id=1029645

    This is simply because I need to finish adding in the LaTeX
    equivalent of the UTC code for these characters. This exists
    as a dictionary in:

    /usr/lib/wyneken/pym/myglobals.py

    named utf.

    Karl

     
  • karlabbott

    karlabbott - 2005-09-28
    • assigned_to: nobody --> karlabbott
     
  • Maxim

    Maxim - 2005-09-29

    Logged In: YES
    user_id=80805

    I uploaded a patch for myglobals.py with all the umlaut
    characters added, all caps added, all circonflex characters
    added and the character added. Don't know what that's
    called though ;)

     
  • Maxim

    Maxim - 2005-09-29

    myglobals.py patch for accented characters

     
  • Maxim

    Maxim - 2005-09-29

    Logged In: YES
    user_id=80805

    Forgot the checkbox.

     
  • karlabbott

    karlabbott - 2005-10-03

    Logged In: YES
    user_id=1029645

    I need to start monitoring bugs as I didn't get any email
    when this one was updated. My apologies, wzzrd, I didn't see
    your work. I think I need to get the code into cvs pretty
    soon. Here is my current utf dictionary.

    utf={173:"\\'{i}",169:"\\'{e}",186:"\\'{u}",161:"\\'{a}",179:"\\'{o}",160:"\\`{a}",168:"\\`{e}",172:"\\`{i}",178:"\\`{o}",185:"\\`{u}",128:"\\`{A}",129:"\\'{A}",130:"\\^{A}",131:"\\~{A}",132:'\\"{A}',133:"\\.{A}",134:"{\\AE}",135:"\\c{A}",136:"\\`{E}",137:"\\'{E}",138:"\\^{E}",139:'\\"{E}"',140:"\\`{I}",141:"\\'{I}",142:"\\^{I}",143:'\\"{I}',145:"\\~{N}",146:"\\`{O}",147:"\\'{O}",148:"\\^{O}",149:"\\~{O}",150:'\\"{O}',152:"{\\O}",153:"\\`{U}",154:"\\'{U}",155:"\\^{U}",156:'\\"{U}',157:"\\'{Y}",159:"{\\SS}",162:"\\^{a}",163:"\\~{a}",164:'\\"{a}',165:"\\.{a}",166:"{\\ae}",167:"\\c{c}",170:"\\^{e}",171:'\\"{e}',174:"\\^{i}",175:'\\"{i}',177:"\\~{n}",181:"\\^{o}",182:"\\~{o}",183:'\\"{o}',184:"{\\o}",187:"\\^{u}",188:'\\"{u}',189:"\\'{y}",191:'\\"{y}'}

    I will be comparing your work and mine to make the most of
    both efforts.

    Again, my apologies.

    Karl

     
  • karlabbott

    karlabbott - 2008-04-08

    Logged In: YES
    user_id=1029645
    Originator: NO

    Interestingly enough, after a little over 2 years, with 0.5.3, we will begin working on UTF-8 support.

     
  • karlabbott

    karlabbott - 2008-04-08

    Logged In: YES
    user_id=1029645
    Originator: NO

    Interestingly enough, after a little over 2 years, with 0.5.3, we will begin working on UTF-8 support.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks