Lost in translation

One important milestone for any Mumble release is freezing the text-strings. After a freeze, no changes are allowed, which means our translators can start working. For this release, we’d like a bit of help proofing and checking the strings before we freeze them.

The usual method for freezing strings is to export them all to a webpage, load that webpage into Word and use the spelling and grammar checker. This catches the worst mistakes, and there always are quite a few. However, it does not catch nuances of language, and it certainly doesn’t catch wrong information.

As I was looking through the strings for this release, I notice that the tooltip for the bitrate in the audiostats mention that you can adjust the bitrate by changing complexity in the audio settings. We replaced the complexity slider with a direct bitrate slider before 1.2.0, so that text has been wrong for quite a few releases. Thankfully, it appears nobody has noticed.

Translations are one of the last hurdles before 1.2.3 ships, and since translations can’t start until strings are frozen, we need a bit of help. The dev team wrote these strings, and we’ve seen them so many times we aren’t really reading them anymore. It’s therefore hard for us to spot mistakes and errors.

So, if you find any spelling, grammar or textual logic errors in the current snapshot, or in the exported strings, please let us know :)

UPDATE: Strings are frozen now. Thanks for your help.

This entry was posted in Community and tagged . Bookmark the permalink.

14 Responses to Lost in translation

  1. fwaggle says:

    My comments were on IRC, and too far in scrollback for me to copy+paste them here… if they don’t get mentioned blame pcgod. :)

  2. DK says:

    “We strongly recommend you store this backup on removable storage, such as an USB memory stick.”
    Should be “a USB memory stick”. I didn’t read through it, just spell-checked it but that’s all I found. Release it already 😀

  3. Redneck Rogue says:

    In several locations the word canceller is used. It should be canceler.

    Noticed it three times in Audio Stats–I would do a replace string on it to be sure you catch them all 😉

    Other than that I didn’t notice anything awry!

  4. Arie says:

    Strange word order:
    This button will restore the settings for the current page only to their defaults. Other pages will not be changed.

    I think something like this is better:
    This button will restore the defaults for the settings on the current page. Other pages will not be changed.

  5. Rawnar says:

    I have made a topic on the forum, as my comment is to long for this blog.

  6. ngollan says:

    Alright, my text got mangled by the markup stripper.

    There are several occurrences of “This [verb]s [something]”, e.g. “This chooses what device to query.”

    Most of the time, those constructs can be reduced to “[verb] [something]”, like “Choose the device to query”, as the context is already given by the string appearing in a tooltip or whatsthis.

  7. pseubodot says:

    Is there anything wrong with using ispell or aspell for spell checking?

  8. 6a209 says:

    i need manul for mumble,but i have not found any manul for mumble~

Leave a Reply