Completed French translation

French locale for Phex

Thanks for the great work. Unfortunately we just recently working on a different translation concept using PO files, with a web editing interface.
It will take some time, but I will try to manually apply your changes into the new web interface.

Indeed, I saw the po files on SVN but they seemed to have several problems: the original strings are not really what must be translated, poedit returns a good bunch of errors when trying to save the file (formatting errors, the charset wasn't detected properly which led to funky stuff being displayed and so on). And being able to test the translation in real time is definitely great (a little history on my Terminal would probably return like java -jar phex.jar) so I went on with the properties file.

Argh, blame that stupid cat walking on the keyboard for the previous message which got posted before I finished it. In fact, I'd like to update the Turkish locale as well so I'll need some guidance: the .properties file has missing strings in English therefore I couldn't work with it, but this was good in some way since you're using a new system.

The problem with the po files is that the ones on SVN seem to have problems: opening and then saving them with poedit returns a good bunch of errors, the original strings are not really what needs to be translated and there are already translated strings which do not appear in Lang_tr_TR.po. What should I do in order to update that locale?

PS: You may want to update, or at least post a little warning on http://www.phex.org/wiki/index.php/Localize_Phex about the new translation system.

Yes I know, there are still problems with it. It was a dissertation work of a student, which was left more or less unfinished.
We have a web interface at http://translate.phex.org, you can register there and I will try to give you access rights.
I would like to solve the po file problems so that its possible to use poedit and other software too. If you find out what the exact problem is, I be happy to change it. The original strings are still the keys from the property files. I think it would require a larger rework of the Phex source to solve this. Currently I have no idea how to easily automate this process.

Just wanted to tell that I'm "converting" the French translation to a .po file so that you don't waste your time with it. I should get it done in a couple of days at worst. I also tested the latest snapshot, I'll soon post both locales with a few corrections.

As a side note, you're certainly aware of it but just in case, note that there's just a little glitch with the po files as of revision 4537: quotation marks need to be escaped. For instance,
...general operation of Phex.<table border="0"><tr>...
needs to be changed to
...general operation of Phex.<table border=\"0\"><tr>...

That would be great. Thanks for your extra work!

Thanks for telling me about the quotation problem. I also saw it while adjusting the po files to conform with poedit. and I was wondering why they only seem to occur in the french file. Maybe they resulted from a bug in a conversion script that was used a while ago.

I also had some trouble converting the Chinese file from unicode or UTF-8 to a po file. Somehow the encoding got messed up.

Well, the couple of days took a bit longer than expected but finally it's done. Both locales can be downloaded from <http://ge.tt/895m5n6> It will be interesting to see them in the snapshots. Please note that I removed all the "/n" strings because they were displayed as plain text.

By the way, will the encoding issue be solved if the Chinese locale is also manually copied over from the properties file to a gettext file?

Thanks again for your work!
I'm not so sure if it was a good idea to remove the \n strings. I think
there is no automatic line wrapping, so it could be that long strings are
just drawn outside the view. The other question is why they are drawn as
plain text. I will check where the problem is.

I found a parsing problem with line breaks, I fixed it and readded the line breaks to the fr and tr files. Hope that was ok for you.

I'm yet not sure what the best approach would be for the Chinese file. I will try to find the problem soon.

Hi there,

Here comes an archive containing slightly modified versions of the Turkish and French locales (typo corrections, reworked keyboard shortcuts, some rewordings, updated © years): <http://ge.tt/92LZFU8> Hope they'll be useful to file sharers with the next version of Phex (which hopefully be released soon given the fact that two major servents do not exist or do not support the network anymore). Also, thanks for reintroducing the \n line breaks, things definitely look better with them.They were missing for ExportDialog_TTTMagnetIncludeXS and for ExportDialog_TTTMagnetIncludeFreebase so I added them there too.

Talking about other servents and as a feature request I think the thing Phex really needs is the Mojito DHT. From the user point of view, it makes a *huge* difference. Same language, same license, hopefully you'll have time to port it.
This git repository may come handy to clone for that purpose: <http://ur1.ca/5b94e>

Thanks again for the update. I added it to SVN. It should be in the next build.
Sorry for the late integration I was busy with relocation and vacation.

No idea how I missed it but in the previous locale I posted AboutPhex_AboutPhex contained the original text in English and then the translation, so here's a corrected version: <http://ompldr.org/iYXplaA>. I also fixed a typo (how can there be an infinite number of typos in a finite number of characters?)

Sorry for bothering you with this again.

No problem, if it makes thinks better, its always welcome. It's in the next build.
Thanks!

Thanks, now that makes a tracker item that can be peacefully closed :) Also, talking about the copyright years, don't forget this one: <http://ompldr.org/iYXpubw>. I know it's masochistic to edit a bitmap image for that and you'll surely do it in a more civilized manner but hey, learning GIMP was fun.

Hope you had happy holidays.

(PS: as a precision, I used Phex 3.4.2.156 regarding my remark on ticket #3419270. I made a mistake by typing 3.4.2.116)

Thanks, I updated the image... :)
I already thought you meant 3.4.2.156, but you would also get 3.4.2.116 if you use the current SVN version. There is no auto update of the build number in SVN, since this would trigger another build. ;-)
So I will put the tracker item on Pending, it will then be closed if you find no more corrections during the next days.

Aaaand.... you were right about the corrections: when the language is switched to French there's a problem with the text displayed by TTTToggleTabActionHide and TTTToggleTabActionShow as shown in this screenshot <http://imageshack.us/photo/my-images/717/phexbutonsbug.gif/>. Comparing with Lang_fr_FR.properties in Phex version 3.4.2.116 it looks like I should have used two apostrophes instead of one, in other words "Cacher l'onglet {0}." should have remained as"Cacher l''onglet {0}." and "Afficher l'onglet {0}." should have remained as "Afficher l''onglet {0}." Testing these changes with Phex 3.4.2.116 suggests that this should fix the issue. If this is the case it may make sense to leave a comment in the po file so that another translation won't make the mistake I made.

As a side question I suspect "General Gnutella Network" should not be translated in SelectNet_NetworkSelectionText as it wasn't in German and as the network name is used as a "password" for private networks but just to make sure, I wanted to ask for a confirmation.

I think I fixed all the strings where this problem might occur. Thanks for reporting it.

Yes, the string <General Gnutella Network> is kind of hard coded, so it makes no sense to translate the reference to it. I also changed that.

I know I am a bother but you'll also need to take care of the Turkish locale in SelectNet_NetworkSelectionText ;)
... için '<Genel Gnutella Ağı>'nı seçin.
could be replaced with
... için '<General Gnutella Network>' değerini seçin.

No problem, quick and easy task. You are not bothering, hints for improvements are always welcome and everyone can benefit.