Re: Translation problems and bad strings

[Åsmund Skjæveland <aasmunds fys uio no>]

[gcalctool]
> msgid ""
> "*** B = %d ILLEGAL IN CALL TO MPCHK.\n"
> "PERHAPS NOT SET BEFORE CALL TO AN MP ROUTINE ***\n"
> msgid ""
> "*** ERROR OCCURRED IN MPROOT, NEWTON ITERATION NOT CONVERGING PROPERLY ***\n"
> msgid "*** ABS(X) NOT LESS THAN 1 IN CALL TO MPEXP1 ***\n"

Should these strings be marked translatable at all?

> * "Antialiasing":

I use a word for "edge smoothing".

I keep running across inconsistent spelling of application names. GDM
uses "gdm" here, "GDM" there. Nautilus and GConf are other examples that
spring to mind. Sometimes I see "GNOME", sometimes "Gnome". When
referring to the binary, lower case is of course correct, but mostly
it's the application name, not the binary, that's discussed.

translator_credits

Some, but not all, of the PO files I translate contains a
"translator_credits" msgid, where the translators fill in their names.

GConf key descriptions

These often contain the possible key values. These values shouldn't
(AFAIK) be translated, but the i18n/l10n docs I've read don't cover
these at all.

As for control, I agree that it's not a good word. A widget is a thingy
on the screen. When I play games, I prefer keyboard controls. I don't
use a spreadsheet to control my spending, but maybe I should.

-- 
Åsmund Skjæveland <aasmunds@fys.uio.no>