Home Forums Wiki Doc Install Extras Screenshots Source Code Projects Blog Users Groups Register
Glx-Dock / Cairo-Dock List of forums Translations | Traductions [Discussion] organizing the .po-files
The latest stable release is the *3.4.0* : How to install it here.
Note: We just switched from BZR to Git on Github! (only to host the code and your future pull requests)
Translations | Traductions

Subjects Author Language Messages Last message
[Locked] [Discussion] organizing the .po-files
Photon English 10 Rob [Read]
12 July 2009 à 21:18

Photon, Friday 10 July 2009 à 12:45


Subscription date : 07 July 2009
Messages : 9
The current state of the .po files is much in need of improvement. First of all the English translation in some places is difficult to understand. There are also some annoying small things (like spaces before colons and question marks, no consistency in upper/lower cases). In several plugins (8 of them) .po files of several languages exist but .pot files don't. Also many general strings exist in all plugins (in fact the whole "Icon" and "Desklet" tabs) and are doubled in all the .pot files thus the translators have to translate them over and over again. It would be much better to have a general "plugin.pot" with those common strings. What do you think, would it be much work to make such changes? At least the latter two things have to be done by one of the devs.

matttbe, Friday 10 July 2009 à 13:33


Subscription date : 24 January 2009
Messages : 12573
It's not a bad idea

First of all the English translation in some places is difficult to understand.
@ fab : Do you apply the correction of pickarooney (available here)?

fabounet, Friday 10 July 2009 à 14:46


Subscription date : 30 November 2007
Messages : 17118
yes there are doubles, personnally I just copy-paste when I translate a .po
I could try to make a general .po files, but not sure it's possible easily because it's very unconvenient to use with the maketools.

@Matttbe I'm afraid I didn't apply them
I was thinking of making en.po files, so that original sentences remain the same (to keep the actual translations)
it wouldn't solve the consistency/understanding of the .pot files though.

matttbe, Friday 10 July 2009 à 14:57


Subscription date : 24 January 2009
Messages : 12573
@ fab : take your time

Photon, Friday 10 July 2009 à 16:02


Subscription date : 07 July 2009
Messages : 9
I don't know how much work it really is but if you would get this done, it would be great, because otherwise each of the translator teams will have to do much unnecessary work for each new plugin and for all the existing ones (and if it's just copy&paste it's still quite much if you consider how many languages there will eventually be)...

fabounet, Friday 10 July 2009 à 18:43


Subscription date : 30 November 2007
Messages : 17118
yep, I'll see if I can do something.
<out of the context>
by the way, it makes me think that we once talked about using cmake ...
as it seems we're going to mess everything, it could be the right moment
</out of the context>

Rob, Sunday 12 July 2009 à 11:22


Subscription date : 10 July 2009
Messages : 30
Maybe translators can make some suggestions that possibly can be changed in the English version, to make it easier for translators and users too.

fabounet, Sunday 12 July 2009 à 13:26


Subscription date : 30 November 2007
Messages : 17118
of course they can
I already have a set of modification to apply on the english sentences.
also it's possible to add some "hint" to a sentence to help translators.

Rob, Sunday 12 July 2009 à 13:58


Subscription date : 10 July 2009
Messages : 30
How do you want us to make a suggestion, fabounet ?

fabounet, Sunday 12 July 2009 à 19:37


Subscription date : 30 November 2007
Messages : 17118
well, how many suggestions ?
if there are few, you can just list them here, otherwise, inside a "en.po" file I think.

Rob, Sunday 12 July 2009 à 21:18


Subscription date : 10 July 2009
Messages : 30
I only have 4 suggestions.

1) Filename of an image to put on :
suggestion, Filename of an image for callbackzone :

2) Distance to the screen's edge :
suggestion, Gap between bottom of the dock to the screen border :
I think gap between bottom, explains what the gap is about and I think sometimes screenborder is easier to understand then screen´s edge. When I think of the screen´s edge, I think of the leftside and rightside but when I here screen border it´s more obvious that it´s all off the screen´s edge.

3) Gap from the absolute position on the screen's edge, in pixels. You can also move the dock by holding ALT or CTRL key and left mouse button.
suggestion, Gap from the sides of the dock to the screen border, in pixels. You can also move the dock by holding ALT or CTRL key and left mouse button.
I think Gap from the sides is easier to understand, screenborder see explanation above

4) At 0, the dock will place itself regarding the left corner if horizontal and the top corner if vertical, at 1 regarding the right corner if horizontal and the bottom corner if vertical, and at 0.5, regarding the middle of the screen's edge.
suggestion, At 0, the dock will place itself in the left corner if horizontal and the top corner if vertical, at 1 in the the right corner if horizontal and the bottom corner if vertical, and at 0.5 in the middle of the screen border.
I think the word regarding is a little bit confusing.

Translations | Traductions

Subjects Author Language Messages Last message
[Locked] [Discussion] organizing the .po-files
Photon English 10 Rob [Read]
12 July 2009 à 21:18


Glx-Dock / Cairo-Dock List of forums Translations | Traductions [Discussion] organizing the .po-files Top

Online users :

Powered by ElementSpeak © 2007 Adrien Pilleboue, 2009-2013 Matthieu Baerts.
Dock based on CSS Dock Menu (Ndesign) with jQuery. Icons by zgegball
Cairo-Dock is a free software under GNU-GPL3 licence. First stable version created by Fabounet.
Many thanks to TuxFamily for the web Hosting and Mav for the domain name.