Hello all
I got a problem, I download and apply the latest PO file and translate the new strings. But every time I try compiling the reversion 878, it will set two strings to fuzzy and don't use the new strings from 879.
I upload the translation and screen shot that shown this problem.
Thank you in advance for any solution.
(12-14-2012, 08:42 AM)Runo Wrote: [ -> ]Thanks Glenn. Did you see this about the Parsi (old Persian) translation?
(11-20-2012, 07:03 PM)Delayline Wrote: [ -> ]I have a request: Farsi is the same Parsi in Arab pronunciation, but it's not related to them! So would you please change it to Parsi?
Persian is wrong too. Because there is no language called Persian as Japanese is the wrong displacement for Nihongo.
Thank you.
Now that raises me a question.. Shouldn't we keep calling it Persian, since it is the name of that language in English? Just as we call Español Spanish, for example.
Do what you think is best. At least Persian is much better than Farsi.
Doesn't poEdit say anything when saving the file (an error or something)?
Major update of Polish translation!
Keep the good work guys!
Those strings are not marked as fuzzy. Strings are marked as fuzzy using the word "fuzzy" in the comment above the msgid line. Those strings are no longer in the source code. The lines that begin with #~ are obsolete translations. Those were in the code at some point and were translated, but have been removed. poedit saves them because they may return to the code at some point. If that happens gettext brings them back automatically.
As to the Parsi/Farsi thing you can change the translation of the language name if you want, but the English version will probably need to remain Farsi or Persian.
(12-15-2012, 12:01 PM)Delayline Wrote: [ -> ]Hello all
I got a problem, I download and apply the latest PO file and translate the new strings. But every time I try compiling the reversion 878, it will set two strings to fuzzy and don't use the new strings from 879.
I upload the translation and screen shot that shown this problem.
Thank you in advance for any solution.
(12-14-2012, 08:42 AM)Runo Wrote: [ -> ]Thanks Glenn. Did you see this about the Parsi (old Persian) translation?
(11-20-2012, 07:03 PM)Delayline Wrote: [ -> ]I have a request: Farsi is the same Parsi in Arab pronunciation, but it's not related to them! So would you please change it to Parsi?
Persian is wrong too. Because there is no language called Persian as Japanese is the wrong displacement for Nihongo.
Thank you.
Now that raises me a question.. Shouldn't we keep calling it Persian, since it is the name of that language in English? Just as we call Español Spanish, for example.
Do what you think is best. At least Persian is much better than Farsi.
Delayline: Are you building agains the translations-update branch? The reason those strings are probably being marked as obsolete is because you are building against the master branch. Those strings are not in the pot file in the master branch. They are in the pot file in the translations-update branch.
(12-18-2012, 01:20 AM)glennric Wrote: [ -> ]Those strings are not marked as fuzzy. Strings are marked as fuzzy using the word "fuzzy" in the comment above the msgid line. Those strings are no longer in the source code. The lines that begin with #~ are obsolete translations. Those were in the code at some point and were translated, but have been removed. poedit saves them because they may return to the code at some point. If that happens gettext brings them back automatically.
I understand what you say.
Quote: As to the Parsi/Farsi thing you can change the translation of the language name if you want, but the English version will probably need to remain Farsi or Persian.
Yes I do. As I said before Persian is better than Farsi because it don't have any relations with Arab world, at least.
Quote: Delayline: Are you building agains the translations-update branch? The reason those strings are probably being marked as obsolete is because you are building against the master branch. Those strings are not in the pot file in the master branch. They are in the pot file in the translations-update branch.
Yes I compiled the master-branch. So with this condition my translation is correct, right?
By the way, thanks for the reply.
I did new pot korean language. Latest POT file version
"POT-Creation-Date: 2012-12-11 08:14-0600\n"
"PO-Revision-Date: 2012-12-18 17:21+0900\n"
I always use Same link just like before in first page, plz check.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[attachment=5034]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Siegfried: Thanks.
All translators should note that there is discussion of a new release of dolphin-emu. This means that if you want your translation to be part of the release it needs to be complete and given to me as soon as possible.
Just updated the Spanish translation at 3.0.879
PD
marked the changes as provisional and made minor corrections in the config options (in my POV))
PD2:deleted wrong attachement
Puniasterus: The file that you provided is compressed using rar, not zip. Please use the appropriate extension so that I know which archiving program to use.