Opened 7 years ago

Last modified 4 years ago

#1664 new defect

Texts in command dialogs are garbled

Reported by: wenzeslaus Owned by: grass-dev@…
Priority: normal Milestone: 6.4.6
Component: Translations Version: unspecified
Keywords: encoding translation, wingrass Cc:
CPU: Unspecified Platform: MSWindows 7

Description

Generated command dialogs show garbled texts. It does not apply to buttons and other strings which comes directly from Python code. It applies to string which comes from module option description (but with some translation activated).

Acutes and other diacritics signs are shown before letters. However this is detail and it can differ between languages/encodings.

It is necessary to test this with language which uses non-ascii characters. System encoding has to be other than UTF-8. It is not known if this can be reproduced on systems other than Windows.

Problem can by in piping and reading piped text. It happens in files:

lib/gis/parser_interface.c
lib/python/task.py

Attachments (1)

diacritics.png (44.1 KB) - added by MilenaN 7 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 7 years ago by hamish

Component: DefaultTranslations
Keywords: wingrass added

can you provide a screenshot? which version of GRASS? which wingrass package? which language(s) did you try? what language is Windows set up to use?

thanks, Hamish

Changed 7 years ago by MilenaN

Attachment: diacritics.png added

comment:2 Changed 6 years ago by neteler

Tested with PL language on Windows 8, the diacritics are still broken as shown in the attached screenshot.

comment:3 Changed 6 years ago by marisn

I'm afraid that this is a variation of #995 and thus it can NOT be fixed for GRASS 6.x. See more here: http://trac.osgeo.org/grass/ticket/995#comment:18

Does it also affect GRASS 7? If yes, then we have to change automatic GUI generation to work around this issue as Microsoft isn't going to change all of broken ways how Windows works :(

comment:4 Changed 4 years ago by martinl

Milestone: 6.4.6
Note: See TracTickets for help on using tickets.