as a translator you need to be a bit creative and flexible.
First there is the user interface. Things should be clear and understandable. Then there are the reports, things have to readable. You will find that in general, for reports there is a distinction between singular phrases and plural. If not, you should open a bug ticket on the bug tracker to mention the problem, so somebody can change it.
Finally there are tools and less important utilities. The programmer could make a distinction between singular and plural, but that really just means more work for everybody. The example you give is from the check tool. You should not translate it literally if it looks dirty. You can translate the phrase:
'Number of broken child/family links found: %d\n'
instead which means just the same.That sentence is just as good as the original sentence, and it doesn't matter if it is plural or not. For the check tool, that is good enough.
So to conclude:
1/for problematic sentences which are in less important places: work around the problem, it is not worthwile to change the English sentence, just be creative in the translation.
2/for problematic sentences which are in reports or prominently in the user interface: open a bug item per problem on the bug tracker.
Example of string in pot file:
msgid "%d broken child/family links were found\n"
It should be replaced with this couple:
msgid "%d broken child/family link was found\n"
msgid_plural "msgid "%d broken child/family links were found\n"
Than I would be able to translate:
msgstr "Najdenih je bilo %d prekinjenih povezav med otrokom in družino.\n"
msgstr "Najdena je bila %d prekinjena povezava med otrokom in družino.\n"
msgstr "Najdeni sta bili %d prekinjeni povezavi med otrokom in družino.\n"
msgstr "Najdene so bile %d prekinjene povezave med otrokom in družino.\n"
BernardOn Jan 24, 2008 10:11 AM, Benny Malengier <firstname.lastname@example.org> wrote:Can you please provide an example of english text you have problems translating, indicating what the problem is?
Benny2008/1/24, Bernard Banko < email@example.com>:-------------------------------------------------------------------------Hello,
I am new to this mailing list and unfortunately I can't code. I am doing
a translation of gramps and I mis the possibility to use proper plural
forms. As I think that the problem is at the source level, I wonder if
there's a possibility to change the code accordingly until the 3.0 is
due. I don't know what exactly is to be done there to give to the
translators the possibility to use msgstr, msgstr and so on. How
is the plural problem dealt in russian translation? (Шура ?) ;-)
Thanks for comments.
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Gramps-devel mailing list