Tirsdag den 2. marts 2010 22:02:07 skrev Carlos E. R.:

On Tuesday, 2010-03-02 at 16:03 +0100, Karl Eichwalder wrote:

...

It's time to think about openSUSE 11.3 translation planning. Which date would work best for you? When must we ask for string freeze, etc.?

I've noted down string freeze on March 25, and translation freeze on June 10. Not sure where exactly I got those dates - but I assume I must have got them from the fancy javascript timeline that coolo keeps somewhere. These dates seem ok to me. Though I'm waiting anxiously for the kde sc 4.5 schedule, which will probably overlap quite a bit with openSUSE 11.3 in terms of translation cycle - which will be hard on me and a few other openSUSE translators.

Wow. I got the 11.2 complimentary dvd less than a month ago, so 11.2 is not yet "officially" installed in my system... and 11.3 is already round the corner. You got me unawares! O:-)

Now that there's a fixed 8 month cycle it shouldn't be too surprising. And mid July is not quite "around the corner" in my book :-)

I don't even know what I'll use for the job, as I don't know if kbabel is available for 11.2 or not...

Lokalize is much better than KBabel ever was - and has been for a while. I guess KBabel is available on the OBS, along with the rest of the heavily bitrotting kde3 stuff. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-03-02 at 23:14 +0100, Martin Schlander wrote:

...

I don't even know what I'll use for the job, as I don't know if kbabel is available for 11.2 or not...

Lokalize is much better than KBabel ever was - and has been for a while.

Las time I looked Lokalize held a lot of promise - but that is, promise. I couldn't figure how to configure it, and I did not find some functionality I need.

I guess KBabel is available on the OBS, along with the rest of the heavily bitrotting kde3 stuff.

which means I will have to keep my 11.0 install and do jobs there. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkuNoPoACgkQtTMYHG2NR9Vf/ACgj/CbSCKMTWESUEQu4zoyWeEU Yc4An0NAdvGVA6dAGxBQYcnLxXS3kNKQ =lXzM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

2010/3/3 Martin Schlander :

Onsdag den 3. marts 2010 00:36:18 skrev Carlos E. R.:

...

On Tuesday, 2010-03-02 at 23:14 +0100, Martin Schlander wrote:

...

Lokalize is much better than KBabel ever was - and has been for a while.

Las time I looked Lokalize held a lot of promise - but that is, promise. I couldn't figure how to configure it, and I did not find some functionality I need.

You guys must be crazy ;-)

The diffs for fuzzy messages alone saves so much time that it can't be exaggerated and is well worth the switch (supported by openSUSE PO-files since 11.2 cycle).

And there's so much else Lokalize does to help you translate better and faster. Sometimes it's almost too easy.

You need to try it again (>= 4.3 version particularly). The time will be a good investment.

I use Lokalize and love it (especially the diffs) but it indeed has some missing funcionality compared to KBabel: * couldn't search/spellchecking a folder (kde) or all .po (you had to open every file and run the spellchecker inside) * the alternate translations is not working (i contact the author + create bug but no response since months) To the coordinators, I suggest use one toolkit called 'translate-toolkit' (python-translate-toolkit in OBS) http://translate.sourceforge.net/wiki/toolkit/index In special the poconflicts tools which shows us strings translated different through .po (like the yasts helps like the "Aborting saving [...]" string And for the update-desktop-files I suggest, at least for the kde strings (as kde 4.4.x is in kde stable now), to do the last merge where upstream translations wins and for the remaining 'our' translation wins. Regards, Luiz -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

El Miércoles 03 Marzo 2010, Andrea Turrini escribió:

On 03/02/2010 04:03 PM, Karl Eichwalder wrote:

...

It's time to think about openSUSE 11.3 translation planning. Which date would work best for you? When must we ask for string freeze, etc.?

Cheers, Karl

I am not able to suggest you the best date for string freeze but the only thing I really care is that it should be a real string freeze: it is frustrating to see lot of work wasted by merge after the string freeze, especially when such merge depends on a (very) low-severity bug fix, on a program improvement, or on irrelevant changes. Obviously merges due to high-severity bug fixes are welcome. Agreed. That, and clear dates for string freeze and translation freeze.

On 03/03/2010 01:58 PM, Luiz Fernando Ranghetti wrote:

...

And for the update-desktop-files I suggest, at least for the kde strings (as kde 4.4.x is in kde stable now), to do the last merge where upstream translations wins and for the remaining 'our' translation wins.

I usually translate update-desktop-files to Italian and I think it is better to mark as fuzzy colliding strings instead of considering upstream translations as winning. We need to check more strings but at least we are sure about the quality of the resulting files. In fact, several times in the past I found different translations for the same string (probably due to different upstream translators) and this makes update-desktop-files not consistent. Moreover, sometimes upstream and openSUSE translators adopt different translation conventions (like: we keep this term in English/we translate it) and also this impacts the consistency of resulting files. Agreed

-- Don't see the world through a window, be open{source}minded, and be free :-) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

2010/3/4 Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2010-03-03 09:17, Martin Schlander wrote:

...

Onsdag den 3. marts 2010 00:36:18 skrev Carlos E. R.:

...

On Tuesday, 2010-03-02 at 23:14 +0100, Martin Schlander wrote:

...

Lokalize is much better than KBabel ever was - and has been for a while.

Las time I looked Lokalize held a lot of promise - but that is, promise. I couldn't figure how to configure it, and I did not find some functionality I need.

You guys must be crazy ;-)

The diffs for fuzzy messages alone saves so much time that it can't be exaggerated and is well worth the switch (supported by openSUSE PO-files since 11.2 cycle).

And there's so much else Lokalize does to help you translate better and faster. Sometimes it's almost too easy.

You need to try it again (>= 4.3 version particularly). The time will be a good investment.

Ok, I'll bite :-)

In my other machine, which has oS 11.2 with gnome, I told YaST to install lokalize and all its dependencies. It runs.

The configuration is confusing.

What is "approved status"? If I press "help" on that dialog, I get the "lokalize handbook", not pointed at the page explaining that dialog.

Approved is not fuzzy anymore, after a review from the team leader. It isn't compulsary, you can ignore it.

I try to configure the project. What is ID? what is the root folder?

The glossary? The glossary is a dictionary of translated word to define yourself (select a word in orignal message and in translated message and right-click>Add to glossary. You can make a glossary for many projects or import a glossary from someone else (your team). The template folder? The folder with the pot files. It isn't use with openSUSE but it's usefull for KDE (and other projects). With the template and

Maybe the one with all branch in it (trunk, stable...) translation folder defined, you'll be able in the overview to see all files PO or POT in the same tree. You can click on an empty translation (a POT) to start a translation, when saving it'll do in the PO folder with PO extension.

The branch folder? The branch folder is the folder of your project translation's version (trunk, stable, for me it's ~/po/opensuse-trunk for the trunk, in this folder I've got the subfolder a folder called wa updated by the svn with the po files.

The alternate translation folder? A folder with old translation files to sync? Not sure. Again, I go to the help file, and under "project" I get just 3 lines of useless text.

How do I display, say, the entire yast/po/es directory, list how many messages each one has (total, translated, fuzzy), check syntax, load one of them? Project > Project overview?

Translation memory.

How do I train it? I want to tell it to scan the entire yast/po/es tree so that it learns. Again, the help file explains nothing. At least, I understand nothing. Choice or create a translation memory, then click Add data and select yast/po/es and wait.

I open a .po file. Open first a project, go to the overview and click on the po file.

What is "phase"? Under the file menu.

I see leds for "untranslated" and "not ready". I don't see "fuzzy". What is "not ready"? How do I get the fuzzy status displayed? How do I change the fuzzy status? Not ready is fuzzy. To change the fuzzy status you've got this red stamp button.

On the left part I see something called "units". What is an unit? I see a link for "add a note". What is a note? Where are the comment fields?

How do I tell lokalize to check the syntax of the translation and then, go to the errors found? I absolutely need this.

Frankly, I can't use lokalize. I can not make head or tails of it. It needs plainly written help, for non programmers. For people used to kbabel. Explaining what is every thing, give examples, explain the intended workflow. It's right there is not much documentation, but as non programmer I didn't find it right. I had just to adapt a bit myself.

Either I use kbabel again, under 11.0, or poedit. KBabel for 11.2 is there: http://software.opensuse.org/ymp/KDE:KDE3/openSUSE_11.2/kdesdk3-translate.ym...

You don't need to keep 11.0 just for KBabel...

- -- Cheers / Saludos,

Cheers aswell, Djan

               Carlos E. R.                (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAkuO8+cACgkQU92UU+smfQWHYwCdGppMNODmpWad80WZeT7SDGvL CTYAnjM9Sw9saZVkEqvetWG2R9Zupp1w =OY5U -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-03-04 09:23, Jean Cayron wrote:

2010/3/4 Carlos E. R.

In my other machine, which has oS 11.2 with gnome, I told YaST to install lokalize and all its dependencies. It runs.

And today it got an automatic update.

The configuration is confusing.

What is "approved status"? If I press "help" on that dialog, I get the "lokalize handbook", not pointed at the page explaining that dialog.

...

Approved is not fuzzy anymore, after a review from the team leader. It isn't compulsary, you can ignore it.

And fuzzy? I don't see a led for it. [ There is something wrong in this thunderbird: my messages get one ">", and yours are getting two. It should be the other way round. New bug? ]

I try to configure the project. What is ID? what is the root folder?

...

Maybe the one with all branch in it (trunk, stable...)

I just wen to create new project, and for project type the options were "kde". No more. The id was set automatically to kde_trunk. I see if I hover the mouse that it says that it diferentiates the memory, so that all kde projects should get the same ID. So the ID should be "openSUSE".

The glossary?

...

The glossary is a dictionary of translated word to define yourself (select a word in orignal message and in translated message and right-click>Add to glossary. You can make a glossary for many projects or import a glossary from someone else (your team).

The glosary for my team is in vertaal, so unless Gabriel bites too and makes a converter... ;-)

The template folder?

...

The folder with the pot files. It isn't use with openSUSE but it's usefull for KDE (and other projects). With the template and translation folder defined, you'll be able in the overview to see all files PO or POT in the same tree. You can click on an empty translation (a POT) to start a translation, when saving it'll do in the PO folder with PO extension.

Yes, I do use the pot directory. In kbabel catalog manager you can see if the number of messages matches in the pot and po files; and in poedit you can tell it to import new messages from the pot file.

The branch folder?

...

The branch folder is the folder of your project translation's version (trunk, stable, for me it's ~/po/opensuse-trunk for the trunk, in this folder I've got the subfolder a folder called wa updated by the svn with the po files.

Ah... I think I see.

The alternate translation folder?

...

A folder with old translation files to sync? Not sure.

It appears that it is for another similar language.

Again, I go to the help file, and under "project" I get just 3 lines of useless text.

How do I display, say, the entire yast/po/es directory, list how many messages each one has (total, translated, fuzzy), check syntax, load one of them?

...

Project > Project overview?

Yes, I got that now. I have this tree: . |-- branches ... | `-- openSUSE-11_2-Branch | |-- lcn | | |-- 50-etc | | |-- 50-html | | | |-- help-boot | | | `-- help-install | | |-- 50-pot | | |-- 50-tools | | `-- es | | `-- po | |-- webyast | | |-- 00-etc | | |-- 00-pot | | `-- es | | `-- po | `-- yast | |-- 50-doc | |-- 50-pot | |-- 50-tools | `-- es | |-- package | `-- po <=== branch folder |-- trunk | |-- lcn | | |-- 50-etc | | |-- 50-html | | | |-- help-boot | | | `-- help-install | | |-- 50-memory | | | `-- bad | | |-- 50-pot | | |-- 50-tools | | `-- es | | `-- po | |-- lokalize-scripts | |-- packages | | |-- 50-etc | | |-- 50-memory | | |-- 50-pot | | |-- 50-tools | | `-- es | | `-- po | |-- webyast | | |-- 00-etc | | |-- 00-pot | | `-- es | | `-- po | `-- yast | |-- 50-doc | |-- 50-memory | |-- 50-pot <=== template folder | |-- 50-proof | |-- 50-tools | `-- es | |-- package | `-- po <=== root folder Just now, I have "root" set to "trunk" above. I understand, from what you people are saying, that I should instead have a project for "yast", and then have: root: trunk/yast/es/po template: trunk/yast/50-pot branch: branches/openSUSE-11_2-Branch/yast/es/po Hah! Lokalize just crashed on me. Nice... signal 11, segmentation fault. Just what I love so much :-/ Well, I repeated all the configuration above. I see that it writes "index.lokalize" to the po directory, and a /lokalize-scripts directory in the same, which then might get uploaded and downloaded from the svn tree. This won't do.

Translation memory.

How do I train it? I want to tell it to scan the entire yast/po/es tree so that it learns. Again, the help file explains nothing. At least, I understand nothing.

...

Choice or create a translation memory, then click Add data and select yast/po/es and wait.

Ah. I selected "trunk" and waited. It worked on some megabytes, but the dialog remained empty. Then I selected "export to tmx", and exported just 186 bytes, nothing. Then I repeated, specifying the .po directory... same result, the TMX file is empty. Is this supposed to work?

I open a .po file.

...

Open first a project, go to the overview and click on the po file.

Ok.

What is "phase"? Under the file menu.

Nothing here.

I see leds for "untranslated" and "not ready". I don't see "fuzzy". What is "not ready"? How do I get the fuzzy status displayed? How do I change the fuzzy status?

...

Not ready is fuzzy. To change the fuzzy status you've got this red stamp button.

Ah, so they changed the name. Why?

On the left part I see something called "units". What is an unit? I see a link for "add a note". What is a note? Where are the comment fields?

How do I tell lokalize to check the syntax of the translation and then, go to the errors found? I absolutely need this.

Frankly, I can't use lokalize. I can not make head or tails of it. It needs plainly written help, for non programmers. For people used to kbabel. Explaining what is every thing, give examples, explain the intended workflow.

...

It's right there is not much documentation, but as non programmer I didn't find it right. I had just to adapt a bit myself.

Adapt a lot, really. Documentation there is next to none.

Either I use kbabel again, under 11.0, or poedit.

...

KBabel for 11.2 is there: http://software.opensuse.org/ymp/KDE:KDE3/openSUSE_11.2/kdesdk3-translate.ym...

...

You don't need to keep 11.0 just for KBabel...

It is an option. I have two machines, an old one with 11.0 (not much free time to upgrade it) and a new one with 11.2. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkuSVcIACgkQU92UU+smfQUOrQCcCP9Q4XYOOrWgqEMTUdmK979X TRoAoJBWcsbFc8d0YyiWwAkMbdBO2cg4 =Y60X -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2010-03-06 at 10:33 -0300, Luiz Fernando Ranghetti wrote:

2010/3/6 Carlos E. R. <>:

...

...

Translation memory.

How do I train it? I want to tell it to scan the entire yast/po/es tree so that it learns. Again, the help file explains nothing. At least, I understand nothing.

...

Choice or create a translation memory, then click Add data and select yast/po/es and wait.

Ah. I selected "trunk" and waited. It worked on some megabytes, but the dialog remained empty. Then I selected "export to tmx", and exported just 186 bytes, nothing. Then I repeated, specifying the .po directory... same result, the TMX file is empty.

Is this supposed to work?

Yes it works. When your have the project configured and showing all the files you could open the translation memory tab and click in 'Rescan project files' (or something similar)

It does, it rescans, but stores nothing. Absolutely nothing, nothing, nothing. A few seconds scanning and I get nothing in the memory.

...

...

What is "phase"? Under the file menu.

The 'phase' concept is more related to Xliff files where you can set diferent phases (similar to what Vertaal does) as translating, reviewing, etc

Ah.

The comments field is in Unit metadada, where you can see the origin of the string, the comment the autor set and/or add you own note (similar to what exists in poedit)

I would prefer the types gettext recommends: comments from translator, comments from devs to translator, etc.

...

...

How do I tell lokalize to check the syntax of the translation and then, go to the errors found? I absolutely need this.

I know that there is a script for kde who check the format and if its wrong it opens Lokalize in the faulty string, but I don't know how to use it nor if it could be used for other projects.

Mmm. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkuSZAUACgkQtTMYHG2NR9UX+QCfXXwo5Yrb/oZSHqh1npbEQf+l Nu8AniS7YGCMUJJaJQ0Zd+4B1W70ljTf =NgHj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-03-06 20:06, Freek de Kruijf wrote:

Op zaterdag 6 maart 2010 15:17:35 schreef Carlos E. R.:

...

It does, it rescans, but stores nothing. Absolutely nothing, nothing, nothing. A few seconds scanning and I get nothing in the memory.

You have to choose in "Tools" "Manage translation memory". Then there is probably a line with "default" in the list box. Select that line.

No such line, the box is empty. Look: http://picpaste.com/Screenshot-Lokalize-memory_1.png

After that you click on "Add data" and you select a directory which contains .po files. You can choose a directory higher in the hierarchy with lower several directories with .po files. After that you will see that in the columns next to default or your chosen line the counts will increase.

It reads the directory alright, but stores nothing, and I see nothing in the dialog. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkuSvvEACgkQU92UU+smfQX/AACgiShWDklNi49MZhVc1Z9RfKdb 5P0AoJJ4QV+O/Qy6pvKFCvHtjaAfinOT =JJGs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Op zaterdag 6 maart 2010 21:45:37 schreef Carlos E. R.:

On 2010-03-06 20:06, Freek de Kruijf wrote:

...

Op zaterdag 6 maart 2010 15:17:35 schreef Carlos E. R.:

...

It does, it rescans, but stores nothing. Absolutely nothing, nothing, nothing. A few seconds scanning and I get nothing in the memory.

You have to choose in "Tools" "Manage translation memory". Then there is probably a line with "default" in the list box. Select that line.

No such line, the box is empty. Look:

http://picpaste.com/Screenshot-Lokalize-memory_1.png

...

After that you click on "Add data" and you select a directory which contains .po files. You can choose a directory higher in the hierarchy with lower several directories with .po files. After that you will see that in the columns next to default or your chosen line the counts will increase.

It reads the directory alright, but stores nothing, and I see nothing in the dialog.

Did you try the create button? You probably did. I can't create. Apart from default I have other names there as well. These can be found in ~/.kde4/share/apps/lokalize/ as default.db together with default.local I start lokalize with --project <project file>. This does not open the project but the project file in Recent opened projects. One of my project files looks like this: [General] BranchDir=/home/freek/vertalingen/svn/oS111/yast/nl/po GlossaryTbx=/home/freek/vertalingen/terms.tbx PoBaseDir=/home/freek/vertalingen/svn/oStrunk/yast/nl/po PotBaseDir=/home/freek/vertalingen/svn/oStrunk/yast/nl/po ProjectID=oSyast/trunk I created /home/freek/vertalingen/svn/oStrunk/yast/nl using cd vertalingen/svn/oStrunk/yast/nl svn checkout https://<u>@svn.berlios.de/svnroot/repos/opensuse- i18n/trunk/yast/nl/po likewise webyast and lcn by replacing yast by these words. Also the oS111 ones. So all in all I have 6 project files for opensuse. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Op zaterdag 6 maart 2010 22:56:11 schreef Carlos E. R.: Did you try to start lokalize in a console. Maybe you find some output there that shows you what is wrong. The output I see, I started with "lokalize -- project <project file>" and finished lokalize after that with <Alt>+F4 and got the following output: 276 277 278 Enchant dict for "nl" 0xb7f0f0 Enchant dict for "nl" 0xb7f0f0 Enchant dict for "en_US" 0xb6d9e0 Enchant dict for "nl" 0xb7f0f0 ** (process:9197): WARNING **: 1 dictionaries weren't free'd. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Op zaterdag 6 maart 2010 22:56:11 schreef Carlos E. R.:

I do have entries in that directory, yes. There are several *.db, of about 26 bytes. The one for opensuse has:

[Personal] FirstRun=false

My default.db is 88 MB and default.local contains the 26 bytes. In the create I entered the name test and now I have a file test.db, but no test.local. This test does not show up in my list. For the other names in my list, except default, I see a file <name>.db and a directory <name> and in that directory either a file trunk.db or branch.db in one case both and sometimes a file branch.local or trunk.local which are always 26 bytes. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Op zondag 7 maart 2010 01:50:51 schreef Carlos E. R.:

On Saturday, 2010-03-06 at 23:39 +0100, Freek de Kruijf wrote:

...

Op zaterdag 6 maart 2010 22:56:11 schreef Carlos E. R.:

...

I do have entries in that directory, yes. There are several *.db, of about 26 bytes. The one for opensuse has:

[Personal] FirstRun=false

My default.db is 88 MB and default.local contains the 26 bytes.

I don't have any *.db anywhere. Only *.local.

Also from the output of starting lokalize in a console it is clear there is something wrong with the database feature. So, maybe, a database package is missing, which is not in the dependency list. So, try to install database packets, until it works. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Op zondag 7 maart 2010 13:40:50 schreef Carlos E. R.:

On Sunday, 2010-03-07 at 09:24 +0100, Freek de Kruijf wrote:

...

...

I don't have any *.db anywhere. Only *.local.

Also from the output of starting lokalize in a console it is clear there is something wrong with the database feature. So, maybe, a database package is missing, which is not in the dependency list. So, try to install database packets, until it works.

That's not feassible, there are hundreds :-(

And anyway, in that case it would complain about a missing library.

With lsof I can see a library with sqlite in the name. So you can check if that one is present. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Søndag den 7. marts 2010 18:36:39 skrev Carlos E. R.:

On Sunday, 2010-03-07 at 14:03 +0100, Freek de Kruijf wrote:

...

...

That's not feassible, there are hundreds :-(

And anyway, in that case it would complain about a missing library.

With lsof I can see a library with sqlite in the name. So you can check if that one is present.

cer@Elessar:~> rpm -qa | grep -i sqlite libsqlite3-0-3.6.16-2.3.x86_64 mono-data-sqlite-2.4.2.3-2.3.x86_64 perl-DBD-SQLite-1.25-2.2.x86_64 libsqlite3-0-32bit-3.6.16-2.3.x86_64 cer@Elessar:~>

Pretty sure you need libqt4-sql-sqlite. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2010-03-04 at 09:23 +0100, Jean Cayron wrote:

...

Either I use kbabel again, under 11.0, or poedit. KBabel for 11.2 is there: http://software.opensuse.org/ymp/KDE:KDE3/openSUSE_11.2/kdesdk3-translate.ym...

You don't need to keep 11.0 just for KBabel...

Kbabel is nowhere to be found: cer@minas-tirith:~> webpin --dist=11.2 kbabel 1 results (1 packages) found for "kbabel" in openSUSE_112 * mtkbabel: Program to Operate the i-Blue 747 GPS Data Logger - 0.8 [Application:/Geo] Even so, I tried installing the two kde3 repos, base and comunity, but yast does not find it. So... is there a procedure to request somebody builds it? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkupYsQACgkQtTMYHG2NR9U2LACeJQkPoUe0gIjU2jHQCVzhcaQz rRQAniF2gfophJOb2mdlUkp3s8htUGCa =Xmv+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-03-24 09:13, Jean Cayron wrote:

Carlos,

Have you even tried the link I gave? There is no so called kbabel package but KBabel is part of the package kdesdk3-translate. Do you try things before asking questions? We give you the solution, you don't try it and say it doesn't work. So why do you ask? Try first to install kdesdk3-translate and see if KBabel is installed or not. If it doesn't work, react then on the list and not the other way round.

KBabel has always been available for 11.2 and no one and nothing prevents you to install it if you follow the instructions.

Sorry, if you told me the specific package where it comes, I didn't notice. I read the message and understood that it is included in the kde3 repo, not that you were telling me that it comes in an specific package. Don't be so harsh. I ask because I didn't see that, and because I couldn't find it. YaST says it is not there, even when told to look at the "provides" list. Webpin can not find it. Why the mistery? Why is it so well hidden? And yes, even before reading your reply, I have kde3 installing at the moment. It will take hours. Some packages fail to download, yst complains about missing kde3base or similar being missing. [...] Well, the install just finished, and kbabel is not installed. I'll have to review things later. Perhaps the path is not in the environment. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkuqQy4ACgkQja8UbcUWM1xfOQEAkPBmHV6WdfhFyWylVIeHCX5e fXv/6/85nyMHCUJBlRUA/jQ3p0iFWzlWfKrmsi/FHvrfZhG4v+Si6W83bJ4ClKzs =5ERJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-03-25 07:14, Jean Cayron wrote:

Hie Carlos,

I noticed that the menu in KDE4 doesn't update all the time when installing new packages. Normally a restart of the desktop solve it. Others you can try to run it as a command Alt+F2 and then kbabel + enter.

I use gnome, not kde4. It failed because, I think, the repo was being updated or something, and some packages failed to install. I got installed some packages related to kbabel, but not the kdesk-... one. After three or four attempts, I finally got it installed and running.

Otherwise, did you try to click on the One click install link I gave? http://software.opensuse.org/ymp/KDE:KDE3/openSUSE_11.2/kdesdk3-translate.ym...

I don't normally use/like them. I prefer installing a repo and installing the "normal" way.

I don't want to be harsh but just thing that when people take time to help you, you should take the time to read carefully their answer before to say that it doesn't work. It's just a matter of respect to the ones that help you.

But anyway, I hope you'll solve it quickly.

This machine is a portable, not the one where I keep my mail archive. I did not have access to your email while I was attempting the install. The problem remains: webpin does not find kbabel: cer@minas-tirith:~> webpin kbabel 1 results (1 packages) found for "kbabel" in openSUSE_112 * mtkbabel: Program to Operate the i-Blue 747 GPS Data Logger - 0.8 [Application:/Geo] Why, I have no idea. YaST doesn't find it until I mark the "provides" box. The New yast webpin tool doesn't find it, either; not even marking "content". There is a problem somewhere. It can be found with another searcher: http://software.opensuse.org/search, though. [...] Hold on, not today, not, it doesn't find it. So I had to ask for help, I booted the other machine and searched for one of the emails that said that kbabel was available, and picked the one I thought best. I read it again, but I did not notice that you were specifying a package. Yes, I made a mistake, but your reaction was a bit harsh. I employ a lot of time helping others, so I think I can claim a bit of leeway for me this time, even if I don't see what I have in front of me for days. Everybody makes mistakes now and then. - - Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkurvHwACgkQja8UbcUWM1xAhgD7Bc8BSQzlr7O/ogmmFqZUaZEU Gn3gHkatEg+zYeRSgd8A/06j+c8ZS9NottTe+aT8RQ7SMHMtyfV3vk9bwvW+P/Fi =pNjg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

...

Ok, I'll bite :-)

Well, seems pretty clear that you don't want to understand, but I'll bite anyway...

Carlos, you are trying to use Lokalize as you did with Kbabel, but they aren't the same program.

...

I try to configure the project. What is ID?

Whatever ID you want for the project

...

what is the root folder?

Where you have your (main) checkout

...

The  glossary?

The glossary.. if you have/want one

You have http://es.opensuse.org/Traduccion/Glosario or more recent: http://www.vertaal.com.ar/iterm/opensuse/es/list/ But you may find some uncomfortable with switching from your browser to Lokalize (or whatever). You may think "integrating the glossary directly in the translation program will be great". If you implement this well you can see all the glossary entries from the words that are in the current english phrase, and you can copy them to the translation field with one click (or one keystroke). This is what you can do with Lokalize. But if you want to do that you have to get the glossary in TBX format (an ISO standard for terminology, aka glossaries), or you can make the glossary word by word using Lokalize (Go to Utilities->Glossary. Maybe this is wrong since I am translating from Galician to English). But frankly I prefer to have an TBX file (a glossary file) and import it to Lokalize.

...

The template folder?

Your checkout of POTs - if you have/want one

...

The branch folder?

In case you want to translate e.g. trunk _and_ 11.2 (branch) at the same time.

...

The alternate translation folder?

Say you translate to pt, maybe you want to look at how pt_br translates the same stuff.

This is an alternate language. To see how was translated in another language some really difficult string.

...

Again, I go to the help file, and under "project" I get just 3 lines of  useless text.

Most of the options have detailed tooltips - try hovering your mouse over stuff for a sec.

...

How do I display, say, the entire yast/po/es directory, list how many  messages each one has (total, translated, fuzzy), check syntax, load one  of them?

project view

...

Translation memory.

How do I train it? I want to tell it to scan the entire yast/po/es tree so  that it learns. Again, the help file explains nothing. At least, I  understand nothing.

Just drag and drop your folder with PO-files on the translation memory toolview, and wait a couple of minutes.

...

How do I change the  fuzzy status?

By translating it or pressing Ctrl+U?

...

On the left part I see something called "units". What is an unit? I see a  link for "add a note". What is a note? Where are the comment fields?

How about you just ignore the features you don't understand/want/need?

Lokalize has integrated support for XLIFF, an standard translation format (not ISO standard yet), and maybe this are things related to that format.

...

How do I tell lokalize to check the syntax of the translation and then, go  to the errors found? I absolutely need this.

You don't. Use some script, there are plenty of them.

...

Frankly, I can't use lokalize. I can not make head or tails of it. It needs  plainly written help, for non programmers. For people used to kbabel.  Explaining what is every thing, give examples, explain the intended  workflow.

Either I use kbabel again, under 11.0, or poedit.

Well. Enjoy.

I really think you should give a try to Lokalize. Poedit has clearly few functionalities, and Kbabel is pretty outdated. If you have complains about Lokalize send them to the developer to help him improve Lokalize. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 06/03/10 10:57, Carlos E. R. escribió:

...

This is what you can do with Lokalize. But if you want to do that you have to get the glossary in TBX format (an ISO standard for terminology, aka glossaries), or you can make the glossary word by word using Lokalize (Go to Utilities->Glossary. Maybe this is wrong since I am translating from Galician to English). But frankly I prefer to have an TBX file (a glossary file) and import it to Lokalize.

Yes, I see the advantage, but I don't have such a file, and I don't know how to make it. Gabriel, are you game?

I'll take a look. - -- Kind regards. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkuSYcYACgkQNHr4BkRe3pLVlwCgwWxtloOvnkdNgYoHeEvDBV+m 0IMAnRx9wqrdgynN/79QG2J/qm6+UJ8l =6RBm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

...

...

This is what you can do with Lokalize. But if you want to do that you have to get the glossary in TBX format (an ISO standard for terminology, aka glossaries), or you can make the glossary word by word using Lokalize (Go to Utilities->Glossary. Maybe this is wrong since I am translating from Galician to English). But frankly I prefer to have an TBX file (a glossary file) and import it to Lokalize.

Yes, I see the advantage, but I don't have such a file, and I don't know how to make it. Gabriel, are you game?

I'll take a look.

Ok. I asked you for this functionality several months ago, and now you are taking a look??? Well, if you need help with TBX format ask me, please!!! Attached is the TBX version of http://www.vertaal.com.ar/iterm/opensuse/gl/list/ but with some additional information (definition, administrative status and description of the glossary). Bye, Leandro Regueiro

Martin Schlander writes:

I've noted down string freeze on March 25, and translation freeze on June 10. Not sure where exactly I got those dates - but I assume I must have got them from the fancy javascript timeline that coolo keeps somewhere. These dates seem ok to me.

Thanks for all your feedback. I'll probably ask the developers next week to submit their preliminary files. Then it would be possible for them to incorporate feedback they receive from the translators. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Andrea Turrini writes:

First feedback/question: is it possible to ask developers to use complete sentences and/or to add more comments into po files?

Sure, it is. Incomplete phrases are not allowed. If you do not know, which developer is working on the tool, please use bugzilla to report bad strings.

For instance, from yast/po/yast2-gtk.it.po: #: src/YGPackageSelector.cc:3299 msgid "" "Failed to create dependency resolver test case.\n" "Please check disk space and permissions for" msgstr "" ...

What is the string that follows "permission for"? the name of a file? of a directory? something else? Translation sometimes depends also on such string, especially when target language distinguishes the genre of words.

In this case, you probably should have added a comment and variable to turn the phrase in a complete sentence: msgid "" "Failed to create dependency resolver test case.\n" "Please check disk space and permissions for %1." -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

As usual, please consider to make use of the SLE11 SP1 translations. Find them in: https://svn.berlios.de/svnroot/repos/opensuse-i18n/branches/SLE11 The following languages were at partially updated for SP1 recently: ar cs da de el en_GB en_US es fi fr hu it ja ko nb nl pl pt_BR ru sv tr uk zh_CN zh_TW Please ask on the list, if you need help with merging or comparison. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org