Open GoogleCodeExporter opened 9 years ago
Runned into the same problem with portuguese, I tend to translate as 'article'
(artigo), and 'to post' as 'write' (escrever).
Original comment by eduardo....@gmail.com
on 22 Jul 2008 at 9:38
I think I have a way to resolve that kind of problems.
Instead of giving english a special status treat it as a regular language that
need a
.po file.
then when a foreign language such as french or portuguese has two translations
for
the same english word, you can change "post" in source code to "post in context
1"
and "post in context 2"
the english "translation" would have the word "post" in two places.
and we would have a way to give distinct words in french or portuguese
according to
the context.
that would be ok ?
Original comment by frol...@gmail.com
on 22 Jul 2008 at 9:50
Indeed, we really should be as specific as possible in the templates, so if
different functions have the same name
in English doesn't mean we are supposed to have that in our languages as well.
I'm going to create a locale/en
for that kind of issues. The English native speakers can than decide if they
want to have detailed strings or not.
Original comment by leidel
on 23 Jul 2008 at 7:08
As I mentioned on IRC, I don't mind more explicit English.
Original comment by jtau...@gmail.com
on 25 Jul 2008 at 8:19
What action do we still need to take here?
Original comment by jtau...@gmail.com
on 17 Aug 2008 at 4:19
@jtauber: we need to have different strings for "post" to make a difference
between a
post that could also be named an article, a note, and the verb to post that
could be
reworded into "publish" for example.
Original comment by frol...@gmail.com
on 20 Aug 2008 at 11:33
Tip about different strings. Use context as a prefix with a separator, like:
_("File menu item ^ Post")
_(Twitter verb ^ Post")
_("Post office") # this needs no context info, it's unambiguous
Original comment by olle.jonsson
on 15 Jan 2009 at 5:38
Original comment by pyDanny
on 13 Mar 2009 at 3:33
Original comment by leidel
on 13 Mar 2009 at 9:06
Original issue reported on code.google.com by
frol...@gmail.com
on 22 Jul 2008 at 9:09