Peter Clifton wrote: > This also has other implications for the smooth operation of gEDA on > your system. If this is failing, you will probably find that printing > (and postscript output) is broken, because that is similarly affected by > "123,10" being emitted instead of "123.10" for decimals.
With the current testing version, screen output and PostScript output is indeed messed up. With the afforementioned second patch applied, screen output is fine, but PostScript output is messed up. > Do you have any further clues as to which gtk-theme settings caused the > issue? I guess it depends on the gtk-theme engine and/or font encoding. > Is it a standard theme I could try here, for example? I am using gtk2-engines-qtcurve. > Do you have any custom gtkrc files? Yes. I am chaning the fg, bg, text colour and font_name="DIN 1451 Mittelschrift" of GtkWidget. The font has ISO-8859-1 encoding only. > Could you post the output of: > > locale LANG=de_AT.UTF-8 LC_CTYPE="de_AT.UTF-8" LC_NUMERIC="de_AT.UTF-8" LC_TIME="de_AT.UTF-8" LC_COLLATE="de_AT.UTF-8" LC_MONETARY="de_AT.UTF-8" LC_MESSAGES="de_AT.UTF-8" LC_PAPER="de_AT.UTF-8" LC_NAME="de_AT.UTF-8" LC_ADDRESS="de_AT.UTF-8" LC_TELEPHONE="de_AT.UTF-8" LC_MEASUREMENT="de_AT.UTF-8" LC_IDENTIFICATION="de_AT.UTF-8" LC_ALL= > locale -a C de_AT.utf8 POSIX > Does running "LC_NUMERIC=C gschem" provide a fix when running "gschem" > on its own is broken? Yes. Screen and PostScript output is fine. HTH -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
