Hi there! it's me again (the new itch of this forum). I've been using ktorrent2.0beta1 for some time now and i have to say the spanish translation is not really good. However, the real problem with this is that the text strings are way too long and when you enable the information window the entire minimum width of the window surpasses 1024 pixels, so if you got a resolution of 1024x768 it doesn't fit the screen. To solve this problem i replaced the sp "ktorrent.mo" with the en_GB version. (/usr/share/locale/es/LC_MESSAGES/ktorrent.mo <--> /usr/share/locale/en_GB/LC_MESSAGES/ktorrent.mo)

I'd help re-doing the sp .mo file, but i have no idea of handling .mo files, so if you want me to translate the strings, tell me how and i'll do it.

(And, also, i think translating some words isn't very neat... for example, even when "leecher" is anyhow properly translated to "sanguijuela" and "seeder" as "sembrador"... it just doesn't sound well...).

Anyway i don't know if it's you who're providing this translation or if they're done by some kind of translator...

Of source you can help improving/updating the translation of your country, (i did it too)

There are local KDE teams who translate po files, listed and downloadable here: http://i18n.kde.org/

These teams do have a coordinator who knows who is working on which project. For the reason of not having more people doing the same work it's wisely to contact this person first so he knows you like to work on it.

I don't know the URL of the spanish KDE team myself though, but you could contact the last translator by email which should be written in the po file here:
http://i18n.kde.org/stats/gui/trunk/es/ ... /index.php

These po files above, they are updated automaticly by a template (pot files) on the server. This updating is all behind the scenes and we (devs, translators) generally have nothing todo with it. (unless you want to do this manually for a quicky)

These po files can be converted to these binary format(ktorrent.mo) with msgfmt. We can do that locally too for the purpose of testdriving the translation, but a translation needs to be uploaded in the po format to the one who has svn/cvs access.

Hope this helps a bit.

The Spanish translation is not the only one showing this. Therefore I think we are going to rearrange the infowidget, so that it fits when the strings are longer.

I'm not quite sure how to rearrange, we can put more things vertically, but then it would become to big in that direction.

How about we move the information in the Chunks groupbox to the Chunks tab and the peers information to the Peers tab ?

I agree that moving it more vertically does have it limits, because how it is now it's already very tiny at 1024x 768 pixels when the logviewer is turned on.

Moving the chunk info box under the assigned chunks in the chunk tab looks like a good idea to me. We could make a poll for it, seeing that finder a good solution for this issue is getting important.
(if poll, maybe waiting until RC and ask on kde-apps to vote on a poll here is a nice idea. Dunno how much work this is, doing just before release...)

Thanks for the info. After i finish with my university exams i'll contact them...

As for the rearrangement, i don't think that's the problem. I mean, the design is quite tidy... The problem is that strings shouldn't be that long, for three main reasons:

1- There's no need for such a thing. (At least in the languages i know...)
2- They completely ruin the design (if they're too long).
3- It's an application, not an ebook... If the strings are too long it's hard to locate the information, as you'll have to read more.

However, it's just my opinion...

J2k, I think the same. When somebody need more information the should use the tooltips and the help (which needs to be made....)

J2k wrote:Thanks for the info. After i finish with my university exams i'll contact them...

As for the rearrangement, i don't think that's the problem. I mean, the design is quite tidy... The problem is that strings shouldn't be that long, for three main reasons:

1- There's no need for such a thing. (At least in the languages i know...)
2- They completely ruin the design (if they're too long).
3- It's an application, not an ebook... If the strings are too long it's hard to locate the information, as you'll have to read more.

However, it's just my opinion...

Some languages are just more verbose then English, and just take more space,

I noticed the update.
Wow this is some clean and sorted infowidget now. It's even prettier then it was before. Good job!!