--Holmes
Thanks!
--Holmes
Thanks for joining and for translating Universal Subtitles. Re:
2011/6/30 Karel Jára <jara....@gmail.com>:
I'd second that, but I believe this is a Transifex setting. However,
as new translation teams must be approved by the maintainers of the
Universal Subtitles translation project, in case people should ask to
create a cs-CZ team, we could simply suggest that they join the cs
team, I gather. Dean? Holmes? What do you say?
Best,
Claude
Re:
2011/6/30 Karel Jára <jara....@gmail.com>:
> One question. How is it that there are some names of languages already
> translated into Czech on the website but there were no strings translated in
> the Transifex when I started translating?
>
See Holmes Wilson's "Lots of new strings" announcement
<https://www.transifex.net/projects/p/universalsubtitles/announcement/732/>
(or on this group, "Tons of new work to do :) "
<http://groups.google.com/group/universalsubtitles/browse_thread/thread/28a3af9574a85ff9>),
June 14, 2011, where he said
"...One thing: some of the new strings are language names, which we
will be translating automatically, but which are still showing up as
untranslated. You can ignore those for now. "
Best,
Claude
After checking the strings that are still untranslated in Italian,
apart from language names Holmes told us would be translated
automatically, 2 strings really beat me:
1) String ID: You can use murkdown. This will replace Description.
Description: None
Comment: -
Occurrences: apps/teams/models.py:89
What is murkdown?
2) String ID: Receive notifications about sends me a message
Description: None
Comment: -
Occurrences: templates/profiles/edit_profile.html:122
Do you mean "Send me notifications when someone sends me a message?
And then, there are quite a few strings with "Suggestions". Pity
Transifex does not seem to offer the possibility to view only those. I
was wondering about starting a common document for all "suggestioned"
strings of all teams (as usually the suggestion expresses a doubt
about the meaning of the string)?
Maybe a Google spreadsheet?
Best
Claude
--Holmes
Markdown. It's a typo and I have just created a ticket for correcting it.
http://en.wikipedia.org/wiki/Markdown
I think it can be translated as is.
>
>
> 2) String ID: Receive notifications about sends me a message
> Description: None
> Comment: -
> Occurrences: templates/profiles/edit_profile.html:122
>
> Do you mean "Send me notifications when someone sends me a message?
This option has been removed, and was another case of jumbled English.
--Holmes
I second Karel's question.
Also: the explanations for the "Typing", "Syncing", and "Review and
make corrections", as well as those for "Translating", within the
subtitling application, don't seem to have transfered into strings to
be translated. Or did I miss them?
And shouldn't the video tutorials of the application be subtitleable
both in English and in other languages?
I am aware that this seems in contradiction with what I wrote you
off-list when new strings got added on June 3, Holmes, about not
adding new strings continuously, lest we translators get discouraged
by seeing our almost finished translations back at a low percentage of
completion. But I believe the above suggested additions would be
fairly light.
Best
Claude
I'll create a ticket for localizing the videos as well.
Both of these things could be a few weeks though. Sorry for the wait.
--Holmes
Best
Claude
2011/7/7 Holmes Wilson <hwi...@gmail.com>:
Same for Italian too: yet the strings covering the home page and the
FAQ pages are all translated, as far as I know, and more than a week
ago.
>
> Regarding the language names, in Czech it’s a bit more complicated and e.g.
> the word “English” might be translated several ways and one is the most
> suitable in one case but another in another case. It can be translated
>
> as the language name “angličtina” and then e.g. a string “English subtitles”
> would have to be translated as “titulky v angličtina” which back to English
> would be like “subtitles in English” but the word “angličtina” is in wrong
> language case in Czech. It should be “titulky v angličtině”. As I suppose,
> language cases are not possible. The language name version is acceptable in
> other places on page.
> as a proverb “anglicky”, which is the current way of how it is translated.
> The string “English subtitles” is very hard to translate with this one
> because “English” is not a proverb but an adjective in that string.
> Currently I have translated it as “titulky anglicky” which doesn’t sound
> much Czech but is bearable. The proverb version is quite suitable in other
> places on the site, e.g. in choosing the languages in profile or in the left
> sidebar of the watch page it is reasonable.
> as an adjective “anglické” which is the most suitable one for translating
> the string “English subtitles” as “anglické titulky” but is unbearable in
> all other places on the page.
>
> The best would be if the language strings could be translated in two
> different ways. One of the options 1 or 2 for most places on the page and
> the option 3 for the strings where the language name is used as an adjective
> together with the noun “subtitles”.
With the proviso that I don't know Czech, Karel, I think I understand
what you say by analogy with other languages. Though we don't have
cases in French and Italian, we do have gender and number agreement,
so a decision problem when we are just given an adjective (and when we
don't know, to boot, whether it's an adjective or a noun). Though
there are some strings for multiple forms, they don't cover all these
instances.
Now each string has a "Suggestion" tab at the bottom. Unfortunately,
these suggestions don't seem to make their way to the people who
manage the strings .po file. So I was thinking: if each team could
mark this kind of issue in their translation, then we could perhaps
collect them all in a single publicly viewable online Google
spreadsheet for the people who manage the original .po file? I'd be
willing to set one up, together with a corresponding form for feeding
the spreadsheet (1),
Other suggestions?
Best
Claude
(1) e.g. with the fields: English string - occurences - translation
language - issue description.