After a short discussion on #licq we figured it's time for a new Licq release. Some bugs have been fixed since 1.3.5, but the biggest change would be the inclusion of qt4-gui. No time plan yet, but I'd say a couple of weeks with release candidates as usual, and then a release. Comments?
Since qt4 is new and all, we also figured this would be a good time to drop translations that aren't maintained and have less than some percentage of strings translated. Is this a good idea, and what should that number be?
But we would of course much rather see the translations become maintained and updated for qt4-gui. So if you prefer to use licq in your native language, please consider becoming the (co-)maintainer for a translation. Or if you don't want to be the maintainer, just doing a single time translation.
Depending on the current status of the translation it will probably require a couple of hours to get it fully translated. But once that is done, it's a matter of doing a limited (but much appreciated) work before every release to get it up to date.
So, if you are interested in updating a translation, reply to this mail and tell us what language you are interested in, and we'll tell you how to proceed.
For current maintainers we would very much like if you would start translating qt4-gui (and update qt3-gui and/or daemon translations). Feel free to respond to this mail as well and tell us that you've started updating the translation.
On Mon, Feb 18, 2008 at 7:51 PM, Erik Johansson <e...@ejohansson.se> wrote:
> Hi all,
> After a short discussion on #licq we figured it's time for a new Licq > release. Some bugs have been fixed since 1.3.5, but the biggest change > would be the inclusion of qt4-gui. No time plan yet, but I'd say a > couple of weeks with release candidates as usual, and then a release. > Comments?
> Since qt4 is new and all, we also figured this would be a good time to > drop translations that aren't maintained and have less than some > percentage of strings translated. Is this a good idea, and what should > that number be?
> But we would of course much rather see the translations become > maintained and updated for qt4-gui. So if you prefer to use licq in > your native language, please consider becoming the (co-)maintainer for > a translation. Or if you don't want to be the maintainer, just doing a > single time translation.
> Depending on the current status of the translation it will probably > require a couple of hours to get it fully translated. But once that is > done, it's a matter of doing a limited (but much appreciated) work > before every release to get it up to date.
> So, if you are interested in updating a translation, reply to this > mail and tell us what language you are interested in, and we'll tell > you how to proceed.
> For current maintainers we would very much like if you would start > translating qt4-gui (and update qt3-gui and/or daemon translations). > Feel free to respond to this mail as well and tell us that you've > started updating the translation.
> For current maintainers we would very much like if you would start > translating qt4-gui (and update qt3-gui and/or daemon translations). > Feel free to respond to this mail as well and tell us that you've > started updating the translation.
> // Erik
Is there any shortcuts for translating the qt4-gui or has that to be done compleatly from the beginning? What tools to use?
I am the current, but not so active, maintainer of the Swedish translation of qt3-gui.
Don't know if I'll have the time to do an update but I'll try if I find the time... I'll be working oncalls several nights the comming weeks so there is not that much time.
> For current maintainers we would very much like if you would start
> translating qt4-gui (and update qt3-gui and/or daemon translations).
> Feel free to respond to this mail as well and tell us that you've
> started updating the translation.
> // Erik
I will try to find time for complete belorussian translation.
---
Усяго найлепшага,
Аляксей Вар'ят aka Kernel panic mailto:Var...@GMail.com
ICQ #202504561
Jabber: Var...@jabber.org.by
2008/2/19, Samuel Blomqvist <salbl...@student.umu.se>:
> Is there any shortcuts for translating the qt4-gui or has that to be > done compleatly from the beginning? What tools to use?
The qt4 translations are based on those done for qt3, so it's not necessary to start from scratch. For swedish the stats are (shown when building): Generated 1004 translations (528 finished and 476 unfinished) Ignored 235 untranslated source texts
The easiest way to get started is to go to http://svn.licq.org/svn/trunk/qt4-gui/po/ and download the language you are about to translate. Then open the file in linguist (the qt4 variant), translate the strings and send the updated file to licq-dev.
But since you most likely want to test the translation first, the procedure looks something like this: 1. svn co http://svn.licq.org/svn/trunk/qt4-gui 2. mkdir qt4-gui/build 3. cd qt4-gui/build 4. cmake .. 5. linguist-qt4 ../po/sv.ts 6. make install 7. licq -p qt4-gui 8. repeat steps 5-7 until satisfied 9. send sv.ts to licq-dev
Status now for qt4-gui is: be, de, es, ru: Fully finished fi, sv, uk: ca 30% translated bg_BG, cz_CZ, hu_HU, it, ja_JP, pl, pt_BR, sr: 20-25% translated fr, pt, tr: 5-15% translated
For old qt-gui the status is: de, es: Fully finished ru, uk: 99% translated (1-2 untranslated strings) be, sv: >90% translated fi, hu_HU, pt_BR: ca 75% translated bg_BG, cs_CZ, it, ja_JP, pl, sr, tr: 50-60% translated fr, pt: 15-30%
/Anders
On fre, 2008-02-22 at 22:29 -0200, Sebastian Renzi wrote:
> Status now for qt4-gui is: > be, de, es, ru: Fully finished > fi, sv, uk: ca 30% translated > bg_BG, cz_CZ, hu_HU, it, ja_JP, pl, pt_BR, sr: 20-25% translated > fr, pt, tr: 5-15% translated
> For old qt-gui the status is: > de, es: Fully finished > ru, uk: 99% translated (1-2 untranslated strings) > be, sv: >90% translated > fi, hu_HU, pt_BR: ca 75% translated > bg_BG, cs_CZ, it, ja_JP, pl, sr, tr: 50-60% translated > fr, pt: 15-30%
> /Anders
As I know there is no big differences between old qt-gui translations file and new QT4 one. Is there any way to merge/convert new qt4 ts-file to old qt3 one?
Addiitionally, I planing to finish belarusian translation for licq daemon in one day.
Am Montag, 25. Februar 2008 10:23:11 schrieb Аляксей Вар'ят:
> As I know there is no big differences between old qt-gui translations file > and new QT4 one. Is there any way to merge/convert new qt4 ts-file to old > qt3 one?
Not that I knew. You can open the .ts files with both linguist versions. But this won't help you much, since the strings are in different source files etc. Just open both files, and do copy and paste, where appropriate.
Arne
-- Dipl.-Inform. Arne Schmitz Phone +49 (0)241 80-21817 Computer Graphics Group Fax +49 (0)241 80-22899 RWTH Aachen University http://www.rwth-graphics.de Ahornstrasse 55, 52074 Aachen, Germany
Excuse me, but I found one missed phrase in my translattion. Please correct it in SVN using attached patch. Now count of phrases in template is equal to one in translations.
> Please add belarussian translations for the Licq daemon.
Commited as r6076. Thanks.
> Excuse me, but I found one missed phrase in my translattion. Please correct it > in SVN using attached patch. Now count of phrases in template is equal to one in > translations.
Committed as r6077.
> How much time I have to complete translations for qt3-gui?
I don't know of any relase plan with fixed dates yet, so just take the time you need to get it finished.
I was actually surprised to see that we had only two (now three) translations for the daemon.
The following is the status I got from make: be: 879 translated messages, 1 fuzzy translation, 1 untranslated message. de: 879 translated messages, 1 fuzzy translation, 1 untranslated message. es: 873 translated messages, 7 fuzzy translations, 1 untranslated message.
It would of course be great if we could get the daemon strings translated to all the languages available for the gui(s).
