Menu

#2016 GUI: non-english chars in directory names not supported

open
nobody
GUI (361)
3
2005-05-29
2005-05-02
clem
No

German users have the directory "Startmenü" (start
menu) on their system, ScummVM displays the umlaut ü
garbled - possibly because no character for that
exists, so it just loads random stuff from that memory
position.

While this display oddity is surely just a minor
annoyance I think it *might* cause problems if you read
random data - maybe some really smart OS would detect
that as buffer/security problem?

Workaround might be to check for every value >max
supported character and replace it by _ or ? or similar
in display (not the string itself, or we can't access
those dirs anymore :-)

clem

Discussion

  • clem

    clem - 2005-05-02

    weird display behaviour with directory names containing umlauts

     
  • clem

    clem - 2005-05-02

    Logged In: YES
    user_id=1138674

    btw, official ScummVM 0.7.1, Windows XP
    screenshot attached

     
  • Max Horn

    Max Horn - 2005-05-02

    Logged In: YES
    user_id=12935

    Known issue, and it's more complex than that: the drawing
    issue is only the tip of the iceberg. Our config file is
    ASCII, and path names in many modern operating / file
    systems use unicode (UTF8) for filenames, so you may not
    even be able to specify the path properly in the config file
    (well, using UTF8, it *should* be possible to use a UTF8
    text editor to modify the config file accordingly, but the
    GUI won't be able to properly render those paths.

    Of course, it still would probably be a good idea to define
    a special symbol which is drawn whenever a glyph is not
    present in a given font.

     
  • Max Horn

    Max Horn - 2005-05-02
    • summary: non-english chars in directory names not supported --> GUI: non-english chars in directory names not supported
     
  • Max Horn

    Max Horn - 2005-05-29
    • priority: 5 --> 3
     
  • Max Horn

    Max Horn - 2005-06-04

    Logged In: YES
    user_id=12935

    Over here, no garbage is drawn. And in fact, our font
    renderer already contains checks, chars which are not
    supported by the font currently are mapped to the space
    character (I guess mapping them to a special symbol instead
    might be better).

    In my case, the OS gives us UTF8 encoded chars, so the ''
    is indeed mapped to two bytes in the string; and those two
    bytes, by chance, happen to be in the range of chars our
    default font supports, so the '' is drawn as 'u' over
    here. Annoying but harmless.