Re: [Geeqie-devel] translation
Thinks are a little erratic. I would say that fixing up what's in git is useful, and it's good to decouple translation progress from a release actually happening. pgpdUa9TUgdOW.pgp Description: PGP signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] translation of documents in French
Laurent Durand a écrit : Hello, I start translating the documentation into French. Thank you for your work at all. Ignace You should be aware that the current documention is not in sync with latest Geeqie (future 1.0). It's mostly a reformated GQView documentation, converted to wiki. During your translation work, please feel free to update english one ;) Most notably we need screenshots, and fixes related to recent UI changes. Btw, thank you for contributing. -- Zas -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Translation
On pá 10. dubna 2009, Laurent Monin wrote: mecatxis a écrit : Independence of this we should look for translators to get all languages updated. Hi! I'm part of the catalan translation team (ca.po). We started working on it! Great ! Thank you all for takink care of tranlations, but remember that the quality of the English strings is not ideal. Please report anything that is not clear / ambiguous / hard to translate. Thanks, Vladimir -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Translation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Do den 9. Apr 2009 um 21:15 schrieb Laurent MONIN: start over reviewing all fuzzy translations. (Well, I also found a bug in gen_translations_stats.sh if there is no fuzzy but untranslated strings in a po file. But that was not subject to fix for now.) Please fix it ;) Done. :) But if the German locales are that bad how would be the other!? I think it is better to have no translation than such wrong ones. I agree, any translation under 50% and older than one year shouldn't go in. Hmm... There is something which jumps into the eye (Is that phrase common in english?): ./gen_translations_stats.sh | grep 989 This tags many languages as outdated. I have another suggestion. How about removing just all fuzzy translations? That might keep the good translations of every language and trews away all ambiguous translations. I think that is a solution to live with. Independence of this we should look for translators to get all languages updated. Regards Klaus - -- Klaus Ethgenhttp://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen kl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBSd8f6p+OKpjRpO3lAQqPJQgAlqp9QuYqZXWif6PnlCb9kwguTm6QouVb F3Gj/RkgteUVCOVMub1kW1XCeNCUf6aHkqv1x9pTuwMcSLdEu96wOiWv2I5h5dWU qsZq8vY9ViGvdvFnwqbAYs6nBiGHtm4C2Qr1U2+1It+SHqpLxTU+jAGFfDFH2CLe T/c3a7FtScUTgp/3I8FfeQPAWsHol8yRbg6cBHHaAbs2i/rodgORso3d98qXhNTs 3BnahmpC4lu9xZsc3kXHzBAPSxVBLGX6D7bNMCs6mwR7xNWSDvOwVtx+P0XsFXdK Q8ft9ChLAG3f81SjWuRONljSRKkaAtfdrht4kqmpwc821QQQg8uobg== =qs2W -END PGP SIGNATURE- -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Translation
Independence of this we should look for translators to get all languages updated. Hi! I'm part of the catalan translation team (ca.po). We started working on it! -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Translation
mecatxis a écrit : Independence of this we should look for translators to get all languages updated. Hi! I'm part of the catalan translation team (ca.po). We started working on it! Great ! -- Laurent Monin aka Zas -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Translation
On Sat, 4 Apr 2009 23:28:31 +0100 Klaus Ethgen klaus+gee...@ethgen.de wrote: Hi, Hi Klaus, I did some update to de.po, the German translation. Within I found something odd. Is it really necessary to translate strings like D65, D75 (well, maybe, could be written other way in Chinese, but I think that is a fix phrase.) or even more %s\n\%s\? This is needed. In french we don't use such double quotes but «» instead for example. About D65 and al. i guess it is almost fixed so imho this can be removed from translatable strings. Additional there is some internationalised strings in cellrenderericon.c which I do not know where it is for and so I am not clear how to translate it. I think that text is just internal used. (Pixbuf Object for strong example) Yes, since those will be never displayed we can drop them from translations. Apart from that I found some cases where the same word has to be translated different in different context. So my first patch add pgettext for this cases. I am not completely sure if I did the implementation correct (well, at least it works). I just copied the gettext.h from my local gettext installation to the src tree and use that header. But I think that is dirty and there must be a other method to use pgettext. The documentation is quiet about the point how to have that function in source it only tells how that function works. I did a full night searching for how to implement those stuff cleanly. Such stuff may help. However, the second patch is the update of the translation. I am at 78% at the moment but will go on the next days. After all I just added myself to the README file. :-) Good work ;) For the other languages, I think it is necessary to rework them at all. In the German PO file I did found many wrong fuzzy translations. Many of them was just stupid but other did negate the sense completely. So I start over reviewing all fuzzy translations. (Well, I also found a bug in gen_translations_stats.sh if there is no fuzzy but untranslated strings in a po file. But that was not subject to fix for now.) Please fix it ;) But if the German locales are that bad how would be the other!? I think it is better to have no translation than such wrong ones. I agree, any translation under 50% and older than one year shouldn't go in. Regards, -- Laurent MONIN aka Zas -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Translation
On ne 5. dubna 2009, Klaus Ethgen wrote: Hi, I did some update to de.po, the German translation. Within I found something odd. Is it really necessary to translate strings like D65, D75 (well, maybe, could be written other way in Chinese, but I think that is a fix phrase.) or even more %s\n\%s\? Additional there is some internationalised strings in cellrenderericon.c which I do not know where it is for and so I am not clear how to translate it. I think that text is just internal used. (Pixbuf Object for strong example) It seems to be Gtk policy to translate such strings, but I agree that it does not make much sense for Geeqie, since we are sure that the strings are not shown in UI. Apart from that I found some cases where the same word has to be translated different in different context. So my first patch add pgettext for this cases. I am not completely sure if I did the implementation correct (well, at least it works). I just copied the gettext.h from my local gettext installation to the src tree and use that header. But I think that is dirty and there must be a other method to use pgettext. The documentation is quiet about the point how to have that function in source it only tells how that function works. I did a full night searching for how to implement those stuff cleanly. Do we really need pgettext? I think that in most cases the problem is already in the English string which should be improved. However, the second patch is the update of the translation. I am at 78% at the moment but will go on the next days. After all I just added myself to the README file. :-) For the other languages, I think it is necessary to rework them at all. In the German PO file I did found many wrong fuzzy translations. Many of them was just stupid but other did negate the sense completely. So I start over reviewing all fuzzy translations. (Well, I also found a bug in gen_translations_stats.sh if there is no fuzzy but untranslated strings in a po file. But that was not subject to fix for now.) But if the German locales are that bad how would be the other!? I think it is better to have no translation than such wrong ones. I would suggest this: 1. releease beta1 (in 2 weeks or so) 2. focus on improving English strings, fix all strings that are ambiguous or hard to understand 3. string freeze, release beta2, ping the original translators 4. beta3 should be fully translated Vladimir -- ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Translation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 5. Apr 2009 um 9:25 schrieb Vladimir Nadvornik: Apart from that I found some cases where the same word has to be translated different in different context. So my first patch add pgettext for this cases. I am not completely sure if I did the implementation correct (well, at least it works). I just copied the gettext.h from my local gettext installation to the src tree and use that header. But I think that is dirty and there must be a other method to use pgettext. The documentation is quiet about the point how to have that function in source it only tells how that function works. I did a full night searching for how to implement those stuff cleanly. Do we really need pgettext? I think that in most cases the problem is already in the English string which should be improved. Hmm It would be easier for the cases I found to change the English strings. However, in some cases this might be difficult. On the other hand, the pgettext might be not so problematic as it is fully included in the gettext.h file. It just adds some functionality to libintl.h. But it might be helpfull to add a shortcut for it (like __ or so). I found two cases. One is delete which can be Entfernen (well it would be better in English as remove) or in the case of a file Löschen. The second case is Location. Location can be geographical (Ortsangabe) or in the filesystem (Pfad). I do not know if there is a way to change the English phrase. There would be other cases with other words and other languages. The English language has many words with indifferent meaning. (Like other languages too.) However, I put the changes in a separate patch so it can be reverted if we have a better solution. I would suggest this: 1. releease beta1 (in 2 weeks or so) 2. focus on improving English strings, fix all strings that are ambiguous or hard to understand That would be a good idea. But that needs to other translators be involved. 3. string freeze, release beta2, ping the original translators Might be difficult. For German translation the last translator did work for gqview. He might not be available anymore. (I put all translators I found in the de.po if you look for.) Is there a recent list of translators? 4. beta3 should be fully translated That would be a good Idea. However to speak for the German translations I think it would be better to live with no translation then with the one before I fixed it. There are many translations which make other meanings for the string. That could be fatal for deletion warnings for example. Maybe we have to start with null translation for some languages. Regards Klaus - -- Klaus Ethgenhttp://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen kl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBSdiBD5+OKpjRpO3lAQpregf/UzE7V7/+y5Gh5tyO9JpRHBG0t+khSbMI OZnzNN03Z4ILCVThJCfzYrJsu8VjN1bRJqF6qEfw33PGSl6stih3s/2bZgSfRBrZ +i+J6nbOSWark7ip0U6jmXwqMQHIwMyKU58h+ON1/9Orv+VYFgwN1RdbZZAz1tTQ feFpbLYxyj3UgrNZitQxlo2fHQ7WE/qGlgdULy/H3mBr2FrKzzC1OFBu/CSbO+ju 7XDGlRYoIIbavFHSTo/56oyBBA2uS8kFG5OVBq8r6URIGPTGL1bpsYt0FR9WC/NJ MNhKaixFMepR9WIn6UY90cyStLWr9mLSvKcs9TxYrFQlcKxevSt66w== =pl39 -END PGP SIGNATURE- -- ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
