[MonoDevelop] Text-affecting bugs

[Michael Hutchinson]

Hi,

On Jan 2, 2008 12:11 PM, André Offringa <offringa at gmail.com> wrote:
> Hey all,
>
> These are some of the bugs that I found while translating MonoDevelop
> into Dutch, as (will be) announced in my previous or next mail (server
> seemed to have some delivery problems), divided into two categories;
> plain textual errors and translation unabilities. My bugzilla account is
> broken, so I figured I'd best mail them to this list; maybe someone else
> can put them on bugzilla.

Will do.

>
> Regards,
> Andre Offringa
>
> == Textual incorrect ==
> * "Layout Managment", should be "Management"

Good catch.

> * in "<i><b>Note:</b> Only Letters, Digits and Underline are allowed."
> underline should be underscore?

Yes. Also, looks like that string is missing a </i>, so I suppose it's
split across multiple lines?

> * Emit Standard Header: emit has to be Apply or Omit?

Nope, "Emit" means approximately the same as the verb "output". It
controls whether the "standard header" is added to new code files.

> * "Use ccache"
> ccache should be cache?

No, ccache is a program for building C programs faster by using a cache.

> * "a Glade# 2.0 project with one window and button" -> uppercase 'a' ?

Probably, though it might be a mis-extracted string. Worth checking.

> * Makefile variable '{0}' not found. Skipping syncing of {1} all
> references for project {2}."
> I don't know what {1} should be, but this seems never to become a valid
> sentence I think.

I agree. We'll need to check this.

> * "Invalid regex for Error messages. : {0}" (2 times)
> extra period

Looks like it, yes.

> * "Custom commands are not supported for autotools based makefiles.
> Ignoring "

I'm not sure. It may be mis-extracted (the Gettext string extraction
doesn't handle concatenated strings in C# right now).

> should have one or three periods.
> * "The desginer could not be loaded."
> desginer should be designer

Yes.

> * "Substitutes the last substring matched by group number number (decimal)."
> Two times "number"

Yes.

> * "The required addin '{0}' is disabled." and "The required addin '{0}'
> is not installed."
> "addin" should be "add-in"

This is debatable, but we do need to standardise it. I'm not sure
which way it'll go -- MD seems to prefer "addin" but GNOME seems to be
heading towards "extension".

> * I don't know what "Load user-specific settings with the document" in
> preferences->save/load should do. Maybe rename it?

MD has *.userprefs files that contain per-user settings for solutions,
for example which files were loaded when it was last closed, which is
what it means by "user-specific settings". Frankly I don't understand
why this is an option, as i can't see why anyone would disable it.
However, the meaning is relatively straightforward and I can't really
think of a better way to explain it.

> * "a Glade# 2.0 project with one window and button"
> should begin with uppercase "A"

You listed this one already :)

>
> == Errors in behaviour (e.g. not translated) ==
> * Almost the entire "regular expression toolkit" window remains English,
> despite my Dutch translations in the .po file.

That's odd. So they're extracted, but not used?

> * Tooltips for Navigate back and forwards buttons leave the underscore
> (used in the menu for the shortcut) in the text

Yes, I see this.

> * Title of "New layout" form is not translated
> * The text "up" that is below the up button in the filebrowser is not in
> the ".po" file, though it is somehow translated to a default Dutch word
> ("op"). However, the translation is incorrect in this context (it means
> "on top of", it should have been "Omhoog"), so it should also be in the
> .po file and translated.

I guess it uses a GTK# stock button, so would use your system's
translations. We can fix this.

> * "Current" schema in preferences->keybindings window seems
> untranslated, as well as the column names "Key Binding" and "Description".
> * In preferences/changelog add-in, the default name and e-mail address
> text-boxes are still in english, thus are untranslated (though their
> labels are translated).
> * The default layout is called "Default", despite language.
> * In the New file dialog, categories like "Deployment" and "Misc", as
> well as their subcategories, are untranslated.
> * Same in "new project" dialog.

Good work! We'll fix these before we announce that strings are
finalised for translation.

-- 
Michael Hutchinson
http://mjhutchinson.com