57 replies to this topic

[teo]

Hi Laeb,
I have some remarks about last release:

1. Third main menu have bigger font size then all another menus. Please change to the same as in the another menus.

2. You inform translators in the easygestures.dtd file about

double quotes (") characters should be coded \u0022 (" character code can be illegal sometimes because not all strings are prevented from parsing).

but it's not fully proper information. This code is good for all entities for tips. For entities used in the .xul file should be '& quot;'.

3. You changed page 1,2,3 names in the customization panel but don't changed in the tips:
Customize in Options/Customizations/Page1 should be Load URL/Script
Customize in Options/Customizations/Page2 should be Run Program Files
Options/Customizations/Page3 should be Queries

4. What about \uxxxx code in the .properties file? Now Firefox properly reading non-latin characters.

[Laeb]

Hi teo,

Thanks for your feedback. I'll update the tips. Could you please make the changes in your locale so that i can add it to eG4.1 before release ?

Concerning the bug on 3rd main menu font size, that's not happening on my side. Can you confirm the bug or give me more details ?

Concerning the double quotes characters, i'm just suggesting to use the same notation in the whole dtd file instead of starting to use the " code then \u0022 code at the end of the file where the tips strings are located.

Concerning \uxxxx code in the .properties file, i'll check that and make the change if needed.

Thanks again.

[teo]

Hi teo,
Thanks for your feedback. I'll update the tips. Could you please make the changes in your locale so that i can add it to eG4.1 before release ?

I was waiting for your answer.

Concerning the bug on 3rd main menu font size, that's not happening on my side. Can you confirm the bug or give me more details ?

See attached pictures.

Concerning the double quotes characters, i'm just suggesting to use the same notation in the whole dtd file instead of starting to use the " code then \u0022 code at the end of the file where the tips strings are located.

See attached picture why we can't use escaped unicode for .dtd files. Mozilla Development Team recommended & quot; for .dtd files. \uxxxx is recommended for .properties files.

Thanks for your answer.
Polish locale tested and released.

Attached Files

•  eg.png   19.13KB   8 downloads
•  eg1.png   23.33KB   19 downloads
•  eg2.png   24.05KB   14 downloads
•  eg3.png   24.61KB   14 downloads

[chuzo]

Spanish (es-ES) locale updated in the WTS

Spanish (Spain) / es-ES

Greetings

[Laeb]

teo: thanks for the updated info concerning the rules about properties and dtd files. I've made the corrections.

chuzo: thanks for your (es-ES) locale. I'll add it in the next version.

[SchS]

hu-HU is done. S

[humbertosartini]

Hi,

Portuguese (Brazilian) / pt-BR localization has been released

[teo]

@Laeb
Please upload to WTS all locales except en-US WITHOUT new and changed strings. New and changed strings should be only in the en-US locale. In this case WTS will be count only translated strings and textboxes to translation (empty) will be displayed on yellow. Now, even your information, if translator see 100% translated file don't check what is in the file inside. You can check es-ES locale which have 'Released' status. Inside 'easygestures.dtd' file are not translated strings because translator saw 100% translation status.

[Pedro]

Hi Laeb,
while I am testing the italian translation I have found a little big problem. The following image show the problem better than words...



I try to enlarge the images in the skin folder but my changes seems useless because the interface doesn't change

Can you help me?

Bye bye

Luca

[Goofy]

ma, non vedo nessun' problemo io

Attached Files

•  easygestures3.png   18.2KB   11 downloads

[Pedro]

ma, non vedo nessun' problemo io

Mmm......

You have to work a little bit more than this to convince me

[Laeb]

Hi Laeb,
while I am testing the italian translation I have found a little big problem. The following image show the problem better than words...



I try to enlarge the images in the skin folder but my changes seems useless because the interface doesn't change

Can you help me?

Bye bye

Luca

Thanks for reporting that Pedro but I've changed this because it's better than displaying the text on two lines and there is no way for now to change the size of the skin according to the length of the text. Can you shorten the text ?

[Laeb]

@Laeb
Please upload to WTS all locales except en-US WITHOUT new and changed strings. New and changed strings should be only in the en-US locale. In this case WTS will be count only translated strings and textboxes to translation (empty) will be displayed on yellow. Now, even your information, if translator see 100% translated file don't check what is in the file inside. You can check es-ES locale which have 'Released' status. Inside 'easygestures.dtd' file are not translated strings because translator saw 100% translation status.

Ok thanks teo, i understand ! I'll upload a new version as soon as possible.

[Laeb]

ma, non vedo nessun' problemo io

[SchS]

I've finished the translation of hu-HU, but I cannot test it, since the downloadable version of eG does not work. When I try to open the preferences of 4.3beta, i get the following error: XML Parsing Error: undefined entity. It's location is chrome://easygestures/content/options.xul line 41, 1. column. I'm using the official Linux build of FF3.5.1.

[markh]

I've finished the translation of hu-HU, but I cannot test it, since the downloadable version of eG does not work. When I try to open the preferences of 4.3beta, i get the following error: XML Parsing Error: undefined entity. It's location is chrome://easygestures/content/options.xul line 41, 1. column. I'm using the official Linux build of FF3.5.1.

Did you insert the locale file into the xpi properly? If you did, there should be no such error as all entities should be accounted for. This type of error message usually indicates an incomplete locale, so please check your locale file

[SchS]

no, i just downloaded the extension from here, and it wasn't working. But the 4.3 final version works, so i managed to test with it.

[markh]

no, i just downloaded the extension from here, and it wasn't working. But the 4.3 final version works, so i managed to test with it.

Well then, that’s behaviour as expected. See this Wiki page or this help file for more guidance