Hi ALL,
The geoserver since version 2.8.x have a problem with pt-BR language.
It seems that the language was created from the Spanish version and was available without the translation complete.
Then, in the pt-BR language exist today terms in Portuguese, Spanish and some even in English.
Can you remove the file properties of the next version of geoserver until the translation is 100%?
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/
Frank usually handles these files … we are using a third party site to manage their creation.
On 19 July 2016 at 06:54, Fernando Quadro <fsquadro@anonymised.com> wrote:
Hi ALL,
The geoserver since version 2.8.x have a problem with pt-BR language.
It seems that the language was created from the Spanish version and was available without the translation complete.
Then, in the pt-BR language exist today terms in Portuguese, Spanish and some even in English.
Can you remove the file properties of the next version of geoserver until the translation is 100%?
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/
–
Jody Garnett
Just a little explanation how translations are used:
I would suggest to have a look at Transfex translations (https://www.transifex.com/GeoServer/geoserver/ for master and https://www.transifex.com/GeoServer/geoserver_stable/ for (still 2.7.x) branch → I have to update it to 2.9.x)
However, which files causes the problems. I would agree to remove untranslated keys. Maybe it makes sense to remove complete files or even port from other branches where it is almost correct
2016-07-20 21:44 GMT+02:00 Jody Garnett <jody.garnett@anonymised.com>:
Frank usually handles these files … we are using a third party site to manage their creation.
–
Jody Garnett
On 19 July 2016 at 06:54, Fernando Quadro <fsquadro@anonymised.com> wrote:
Hi ALL,
The geoserver since version 2.8.x have a problem with pt-BR language.
It seems that the language was created from the Spanish version and was available without the translation complete.
Then, in the pt-BR language exist today terms in Portuguese, Spanish and some even in English.
Can you remove the file properties of the next version of geoserver until the translation is 100%?
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/
Frank,
I have received some emails complaining about this issue of internationalization, in the case of the Portuguese.
Because of this, I published on my blog, a post teaching how to get back GeoServer into English.
http://www.fernandoquadro.com.br/html/2016/07/21/problema-na-internacionalizacao-do-geoserver/
But as I said in the last email, I think you should evaluate the possibility to remove the pt-BR language until it is 100% complete.
Best regards,
2016-07-20 17:40 GMT-03:00 Frank Gasdorf <fgdrf@anonymised.com>:
Just a little explanation how translations are used:
- origin language is English
- if a properties file exists for another language, existion properties are kind of overwritten
- if the translation is not 100% only translated properties are taken from your prefered language file, everything else comes from the origin properties file (GeoServerApplication.properties)
- in the past new keys in origin files were copied into every other existing properties file to indicate there is something to do
- Transifex handles it quite different ( and follows i18/i10 guidelines) and doesn’t write “un-translated” properties
I would suggest to have a look at Transfex translations (https://www.transifex.com/GeoServer/geoserver/ for master and https://www.transifex.com/GeoServer/geoserver_stable/ for (still 2.7.x) branch → I have to update it to 2.9.x)
However, which files causes the problems. I would agree to remove untranslated keys. Maybe it makes sense to remove complete files or even port from other branches where it is almost correct
–
Frank
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/
2016-07-20 21:44 GMT+02:00 Jody Garnett <jody.garnett@anonymised.com>:
Frank usually handles these files … we are using a third party site to manage their creation.
–
Jody Garnett
On 19 July 2016 at 06:54, Fernando Quadro <fsquadro@anonymised.com> wrote:
Hi ALL,
The geoserver since version 2.8.x have a problem with pt-BR language.
It seems that the language was created from the Spanish version and was available without the translation complete.
Then, in the pt-BR language exist today terms in Portuguese, Spanish and some even in English.
Can you remove the file properties of the next version of geoserver until the translation is 100%?
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/
Would you please give us a list of problematic files (mixed-up with Spanish/English) we can work with. Its quite hard for non natives (of Portuguese) to find out which phrases are wrong.
If possible, please review Transifex project (for Master-Branch) to cleanup untranslated / wrong translations. At the end the translation state will hopefully much mor realistic than it is right now.
Regards
Frank
2016-07-21 13:59 GMT+02:00 Fernando Quadro <fsquadro@anonymised.com…>:
Frank,
I have received some emails complaining about this issue of internationalization, in the case of the Portuguese.
Because of this, I published on my blog, a post teaching how to get back GeoServer into English.
http://www.fernandoquadro.com.br/html/2016/07/21/problema-na-internacionalizacao-do-geoserver/
But as I said in the last email, I think you should evaluate the possibility to remove the pt-BR language until it is 100% complete.
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/
2016-07-20 17:40 GMT-03:00 Frank Gasdorf <fgdrf@anonymised.com>:
Just a little explanation how translations are used:
- origin language is English
- if a properties file exists for another language, existion properties are kind of overwritten
- if the translation is not 100% only translated properties are taken from your prefered language file, everything else comes from the origin properties file (GeoServerApplication.properties)
- in the past new keys in origin files were copied into every other existing properties file to indicate there is something to do
- Transifex handles it quite different ( and follows i18/i10 guidelines) and doesn’t write “un-translated” properties
I would suggest to have a look at Transfex translations (https://www.transifex.com/GeoServer/geoserver/ for master and https://www.transifex.com/GeoServer/geoserver_stable/ for (still 2.7.x) branch → I have to update it to 2.9.x)
However, which files causes the problems. I would agree to remove untranslated keys. Maybe it makes sense to remove complete files or even port from other branches where it is almost correct
–
Frank
2016-07-20 21:44 GMT+02:00 Jody Garnett <jody.garnett@anonymised.com>:
Frank usually handles these files … we are using a third party site to manage their creation.
–
Jody Garnett
On 19 July 2016 at 06:54, Fernando Quadro <fsquadro@anonymised.com> wrote:
Hi ALL,
The geoserver since version 2.8.x have a problem with pt-BR language.
It seems that the language was created from the Spanish version and was available without the translation complete.
Then, in the pt-BR language exist today terms in Portuguese, Spanish and some even in English.
Can you remove the file properties of the next version of geoserver until the translation is 100%?
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/
I cleaned up a bit at Transifex (stable) and removed translations where the origin value was still used as translation. However, I guess it makes sense to write a little script that cleans up the whole bunch of GeoServerApplication_XX.properties files for a branch.
Still it would be a problem to identify wrong translation (in case its Spanish). Here it makes sense to review strings and if not correct to remove translation or even better change it to Portugiese.
Maybe its worth to call GeoServer Transaltion Team (https://www.transifex.com/GeoServer/teams/45000/pt/) for a transpation sprint to review and correct it for master (https://www.transifex.com/GeoServer/geoserver/dashboard/)
Regards
2016-07-20 22:40 GMT+02:00 Frank Gasdorf <fgdrf@anonymised.com>:
Just a little explanation how translations are used:
- origin language is English
- if a properties file exists for another language, existion properties are kind of overwritten
- if the translation is not 100% only translated properties are taken from your prefered language file, everything else comes from the origin properties file (GeoServerApplication.properties)
- in the past new keys in origin files were copied into every other existing properties file to indicate there is something to do
- Transifex handles it quite different ( and follows i18/i10 guidelines) and doesn’t write “un-translated” properties
I would suggest to have a look at Transfex translations (https://www.transifex.com/GeoServer/geoserver/ for master and https://www.transifex.com/GeoServer/geoserver_stable/ for (still 2.7.x) branch → I have to update it to 2.9.x)
However, which files causes the problems. I would agree to remove untranslated keys. Maybe it makes sense to remove complete files or even port from other branches where it is almost correct
–
Frank
2016-07-20 21:44 GMT+02:00 Jody Garnett <jody.garnett@anonymised.com>:
Frank usually handles these files … we are using a third party site to manage their creation.
–
Jody Garnett
On 19 July 2016 at 06:54, Fernando Quadro <fsquadro@anonymised.com> wrote:
Hi ALL,
The geoserver since version 2.8.x have a problem with pt-BR language.
It seems that the language was created from the Spanish version and was available without the translation complete.
Then, in the pt-BR language exist today terms in Portuguese, Spanish and some even in English.
Can you remove the file properties of the next version of geoserver until the translation is 100%?
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
http://br.linkedin.com/in/fernandoquadro/