-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 27/07/2010 18:03, Denis Barbier a écrit : I made most of the changes already, and Denis began to update the website (so I unfuzzied everything possible in po/www/). Since the website is mostly build from the manual pages, I also began to unfuzzy the content of po/pod/. French is up to date, Italian (which translation was not complete), is unfuzzied, and Japanese (which translation was complete) is unfuzzied too: from 1281t 195f 1u, it became 1465t 11f 1u. Any help is welcome for unfuzzy Catalan, Spanish, Polish and Russian: as Denis said, it's not a call for translation, some strings are likely to change again a bit, just a call for unfuzzy help (Omar, if you're still there ;-), just announce it here in order not to duplicate this "funny" work. If nobody talks, I'll try to finish them tomorrow afternoon or evening (European time). Cheers David

On Wed, Jul 28, 2010 at 09:44:32AM +0200, Omar Campagne wrote: Just checked it out. pod checked. No fuzzies in Spanish, unfuzzied catalan as much as I could, and Polish is also up to date. Russian unfuzied too. I assume you didn't spree the style changes yet to the po/pod files. Regards, -- Omar Campagne Polaino

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 28/07/2010 07:00, Denis Barbier a écrit : I didn't want to impose the method, so I didn't updated fuzzy PO. I've used two method yesterday. First, you need to update the PO files in a copy of the repository, and compare the new fuzzy one and the initial, and then: - - edit the initial one and perform preventive unfuzzy (it's quite handy for incomplete translation, in order to spot new fuzzy strings). when it's done, it's possible to do update the PO file and verify nothing has been forgotten. - - edit the generated one, and perform unfuzzy after, it's better on previously complete translation: if a string is fuzzy, it's because of the new mess, not some older stuff. Omar, if it's OK with you, I just updated the Spanish translation, so you can use the second method on this one (I guess that was your intention). Cheers David

Wow David, amazing work. Please note, however, that some of this changes are a bit cultural, so to speak i.e. Locale... - Convert --> Locale... - convert or the deletion of the article in the example lines i.e # The line containing... -> # Line containing... (english can be more concise than other languages) as well as the use of minor letters instead of capital ones in some examples. OTOH, the bulk of changes are po -> POD, sgml -> SGML and more, which do apply. I initially used only «po» given the inconsitency between appereances. I mention this so you do not get surprised if you don't see all changes taken into other translations. As a last note, now you gonna make me do the stylistic brush up I wanted to do for Spanish long ago. Things look good in Spanish, just wanted to see where I could get more «elegant». Thanks, -- Omar Campagne Polaino

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 28/07/2010 15:21, Omar Campagne a écrit : To be honest, the goal was to unified what was already done : Some short synopsis began with a cap, some didn't, now they all begin without cap (like debian packages synopsis should), but if it's more usual to begin with a cap here, we can unify the other way around. Same her, most comments (in the same page or others) didn't begin with cap, so I unified with what was done. Most of the time, the goal was to reach some consistency with the other parts of the documentation. It's not rock stable: we can unify one way or the other ;-). gettext official manual use "PO", so I really think it's better here. I take care of most of the unfuzzy, but it's up to translators to unify the way they prefer (actually, in some languages, and some parts of the documentations, it was already unified the "new" way). I thought it was not fair to ask translators to take care of these issues, making their translation ~15% fuzzy, so I continue... Great, and thanks for taking care of your own translation, it's better to "cleverly" unfuzzy, I mean when you understand what you are messing up ;-). Thanks, do you prefer me to upload the fuzzy Catalan translation too once I'm done ? Actually, while carefully unfuzzing, I spot some style stuff I forgot to made (or upload :/), so anyway, I will upload Spanish translation fuzzy again tonight if that's OK with you. Hope I will be done tonight for the documentation (except Spanish and Catalan), and may begin to unfuzzy po/bin... Anyway, as already announced, strings are likely to change again a bit. Cheers David

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 28/07/2010 16:52, David Prévot a écrit : Done (except Catalan and Spanish which are committed fuzzy), we may review the original strings before asking for translation. For example, I changed the example part of po4a(1), thanks for reviewing it. Is there an easy way to automatically build those files? Am I missing something, or is it broken somewhere? (I manage to "make po4a.pot" and "msgmerge -U fr.po po4a.pot" in order to unfuzzy the French translation, but I wonder if I need to manually do this for every language, or try to add its support in a target somewhere... Cheers