Gentoo Forums
Gentoo Forums
Quick Search: in
Portage Localization
View unanswered posts
View posts from last 24 hours

rackathon
 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
ryszardzonk
Tux's lil' helper
Tux's lil' helper


Joined: 18 Dec 2003
Posts: 138
Location: Rzeszów, POLAND

PostPosted: Wed Sep 20, 2006 2:33 pm    Post subject: Portage Localization Reply with quote

Hi. There is this idea I mentioned in this thread http://forums.gentoo.org/viewtopic-t-499023.html that portage could inform user of its actions in their respective languages. One way of starting that project could be substituting fail messages "install failed" with let's say "${instfail}" and through using of an e-class there could be added "inherit nls" to the ebuild that would do all the magic of finding out users ${LANG} setitng and substitute "${instfail} with proper message.
Same could be done for all other messages. :idea:
Any thoughts on that :?:

Is there anything of that sort of work being done :?:
_________________
Sky is not the limit...
Back to top
View user's profile Send private message
Genone
Retired Dev
Retired Dev


Joined: 14 Mar 2003
Posts: 7742
Location: beyond the rim

PostPosted: Wed Sep 20, 2006 4:45 pm    Post subject: Reply with quote

Not going to make many new friends with this opinion, but I personally dislike localization of system tools, mainly for support reasons.
My biggest concern are translated error messages in bug reports (IMHO error messages should be canonical and translations of them should be outlawed). It really sucks to get bug reports that are useless because the error message is translated (and therefore useless).

Also in my experience translations in free software are often ... less than perfect. I mean at one point I had to install the english version of a program to understand what an option meant as I didn't understand the translated label (hint: don't translate the term "port" in a network configuration dialog). Also for gcc error messages I often have no clue what the translated error messages mean when the english version is perfectly clear. Maybe things have gotten better recently or maybe those were exceptions.

And finally I'm worried what kind of users this would attract. I know this is going to trigger the "gentoo devs are elitist" posts but I think that people administrating Gentoo systems should have a somewhat technical understanding, and understanding english is part of that.

Not to mention the additional maintentance and added complexity issues this would bring with it.

If anyone wants to work on this, fine, but you probably have to do this on your own and if you want to get it merged you better come up with a very good plan and implementation.
Back to top
View user's profile Send private message
daschapa
n00b
n00b


Joined: 01 Sep 2006
Posts: 70
Location: Paraná, Argentina

PostPosted: Wed Sep 20, 2006 5:00 pm    Post subject: Reply with quote

Genone wrote:
Not going to make many new friends with this opinion, but I personally dislike localization of system tools, mainly for support reasons.
My biggest concern are translated error messages in bug reports (IMHO error messages should be canonical and translations of them should be outlawed). It really sucks to get bug reports that are useless because the error message is translated (and therefore useless).

Also in my experience translations in free software are often ... less than perfect. I mean at one point I had to install the english version of a program to understand what an option meant as I didn't understand the translated label (hint: don't translate the term "port" in a network configuration dialog). Also for gcc error messages I often have no clue what the translated error messages mean when the english version is perfectly clear. Maybe things have gotten better recently or maybe those were exceptions.


Excuse my english.
I concur partially with you. But, watta 'bout include a "--locale" parameter. It is some way self-explaning. It may include a warning like "Do not post bug reports with translated outputs".
However, anyone willing use consoles surelly manages some english. If it doesn't... it should.
Anyway, an optional localization (by specifying the corresponding parameter) would be cute. You can say: "Look, Mr. Customer, your system is emerging. Now it will be updated" LOL.
Again, excuse my english (a bad bad bad one). I can read it, but I should never write a word.
Be lucky.
_________________
======================
#emerge -uD full-knowledge

Daschapa Scaramanzia
http://banderas-en-tu-corazon.blogspot.com
Back to top
View user's profile Send private message
ryszardzonk
Tux's lil' helper
Tux's lil' helper


Joined: 18 Dec 2003
Posts: 138
Location: Rzeszów, POLAND

PostPosted: Thu Sep 21, 2006 1:31 pm    Post subject: hard job... Reply with quote

I must say those points are quite valid and sure would need to be really taken into consideration, but noone said it would be easy and the last sentence of yours does not look to promissing as I sense there what I would call hostility toward it. I hope that not all devs have this attitude., but I'll try to motivate You and maybe others toward it.
First I'll answers your words
Quote:
Not going to make many new friends with this opinion,

I may be wrong, but I think that most people using open source are not native english speakers and that there is no reason they shuold not welcome that themselves therefore I count for more ot them being friendly towards it
Quote:

My biggest concern are translated error messages in bug reports (IMHO error messages should be canonical and translations of them should be outlawed).
There is no reason to believe so as option could be DISABLED by default and just like Genone said it below the big bat warning could be added for users not to send this kind of bugs. Even then sure some would be send, but not to make devs life pain in the a*s, but from sense of help they would seek. I do not believe that people like to be humililated in public so much that they would keep sending them. I think that someone who had the knowledge to set it up in they language would be able to revert it at any time and sinse he has knowledge of changing config files I can say with great probability of it being truth that he could write better bug reports than the person that was never able to do it in the first place.
Quote:

Also in my experience translations in free software are often ... less than perfect.

That is just a reson that not all translations should be done at once, but not that they shouldnt be done at all. To help this problem in the beggining for most users the ${instfailed} messages would default to english and translators or at least head translators would be chosen only among those that have a good track record of doing it properly. By the way the translations of the Gentoo Weekly Newsletter are somehow made and I am yet to hear about it being done in the way that they were unable to reach the peple they were directed for becouse of wrongfull translations
Quote:

I mean at one point I had to install the english version of a program to understand what an option meant as I didn't understand the translated label (hint: don't translate the term "port" in a network configuration dialog).
All you saing here is that you could not use the program becouse it was not in your native language and that the software you used could not change language easily. If however you were native speaker of that language that what you should probably do in spirit of open source is file the bug report of translation being done inproperly.
Quote:

And finally I'm worried what kind of users this would attract. I know this is going to trigger the "gentoo devs are elitist"
Yes there are and it can be seen among those that are crearly agaist improving Graphical Instalator as that would simply bring tons of noob questions in the forums or IRC. However no one can say for sure that localization project would degrade Gentoo quality.
Quote:
posts but I think that people administrating Gentoo systems should have a somewhat technical understanding, and understanding english is part of that.
I do agree that people should have some basic knowledge of english as it clearly is international language for all of us, but we should not take away peoples little sense of pride in their native language and just close the issue becouse of this.
Quote:

Not to mention the additional maintentance and added complexity issues this would bring with it.
This is the argument that I hear all the time when something new is to be done.
1) There is not that many translations to be done and they would not change from week to week therefore pepople doing the Weekly Newsletter could take care of this in their free time as there is no need to bring the translation as soon as posibble.
2) Every dev says there is not enough of us to handle to work, and I agree many of you are overvelmed with issues but if someone wants to use their time and knowledge to help than there is this big security question that appears and just refreins devs form using new participants... It is either this or that, please decide for once...

Now to sumarize I believe Portage Localization of being quite meaningful idea and thing to think about. You said that people doing that should have the plan. Well dont all the things in Gentoo start with the plan first? I sure hope not to hear otherwise. There is this place to write such a ides and is called GLEP. That is a fine starting point for that work and will be happy to see someone giving it some time and putting it into next GLEP.
_________________
Sky is not the limit...
Back to top
View user's profile Send private message
Genone
Retired Dev
Retired Dev


Joined: 14 Mar 2003
Posts: 7742
Location: beyond the rim

PostPosted: Thu Sep 21, 2006 5:53 pm    Post subject: Re: hard job... Reply with quote

ryszardzonk wrote:

Quote:

I mean at one point I had to install the english version of a program to understand what an option meant as I didn't understand the translated label (hint: don't translate the term "port" in a network configuration dialog).
All you saing here is that you could not use the program becouse it was not in your native language and that the software you used could not change language easily. If however you were native speaker of that language that what you should probably do in spirit of open source is file the bug report of translation being done inproperly.

I was actually talking about a program translated in my native language, just that particular translation didn't make any sense to me. It wasn't wrong btw, just extremely confusing IMHO.

Quote:
Now to sumarize I believe Portage Localization of being quite meaningful idea and thing to think about. You said that people doing that should have the plan. Well dont all the things in Gentoo start with the plan first? I sure hope not to hear otherwise. There is this place to write such a ides and is called GLEP. That is a fine starting point for that work and will be happy to see someone giving it some time and putting it into next GLEP.


Well, there are plans and there are "plans". Some people might consider "add gettext support" to be a plan. But there is quite a bit more to do for this before it could be considered to be accepted.


Last edited by Genone on Sun Oct 21, 2007 3:51 pm; edited 1 time in total
Back to top
View user's profile Send private message
ryszardzonk
Tux's lil' helper
Tux's lil' helper


Joined: 18 Dec 2003
Posts: 138
Location: Rzeszów, POLAND

PostPosted: Thu Oct 05, 2006 2:19 am    Post subject: Localization Bump Reply with quote

Well, first of all *bump*

I've searched the forum for this issue and found that it actually has been discused in the past, primarly in this posts
http://forums.gentoo.org/viewtopic-t-102421-highlight-portage+localization.html and http://bugs.gentoo.org/show_bug.cgi?id=13618.
Among other reasons to get translation implemented the people there provided the idea that the portage itself dont have to be translated at present however the strings themselves should be as it a good practice to do so. What personaly struck me is that this threads are as early as year 2003. Reasoning behind leaving the issue behind back then was that portage envolves to fast and it would be to much work. There has been several portage rewrites since then practicly from ground up and I am stunned that there is simply no place for translantable strings to make their way into portage. One would think that when the rewrite happens it is a good moment for it. My question now is, do we wait even longer for portage to grow even further to make the move almost imposible or someone steps up for the rest of as and make it happen... I believe it would be worth the effort.

Quote:
..."add gettext support" to be a plan.
Well it is not a plan it is an issue for which the plan would need to be implemented
_________________
Sky is not the limit...
Back to top
View user's profile Send private message
yngwin
Developer
Developer


Joined: 19 Dec 2002
Posts: 3537
Location: in the Dutch Mountains ;-)

PostPosted: Thu Oct 05, 2006 4:29 am    Post subject: Reply with quote

Genone wrote:
Not going to make many new friends with this opinion, but I personally dislike localization of system tools, mainly for support reasons.
My biggest concern are translated error messages in bug reports (IMHO error messages should be canonical and translations of them should be outlawed). It really sucks to get bug reports that are useless because the error message is translated (and therefore useless).

Also in my experience translations in free software are often ... less than perfect.

I hear you, and I do agree with you. Even as an experienced user trying to help people on the forums, non-English error messages just are confusing. Even when they are in my own language (I am moderator on a Dutch Linux forum) you often scratch your head: what the heck do they mean here? Because you get so used to the English terms and error messages. (personally, I use default language on system, and en-GB for desktop)

One possibility is a compromise: when localized, let portage print error messages in both English and the localized language, that way the support issue is still met, and the user gets a localized message as well. I know this is a bit ugly, but I think it's workable.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
ryszardzonk
Tux's lil' helper
Tux's lil' helper


Joined: 18 Dec 2003
Posts: 138
Location: Rzeszów, POLAND

PostPosted: Thu Oct 05, 2006 3:37 pm    Post subject: step forward Reply with quote

yngwin wrote:
One possibility is a compromise: when localized, let portage print error messages in both English and the localized language, that way the support issue is still met, and the user gets a localized message as well. I know this is a bit ugly, but I think it's workable.
For me it sounds good. I dont think it would satisfy everyone and probably would just make most switch to plain English sinse who would want for longer time see redundant messages ;). However it I think it is a step in the right direction and would vote for implementing this if required. I can imagine that language skills of international users about which developers (not without the reason) are quite afraid could potentially improve . Of course his would not substitute proper English lesons, but sure enough to learn as Genone put it canonical error messages.
_________________
Sky is not the limit...
Back to top
View user's profile Send private message
chrbecke
Guru
Guru


Joined: 12 Jul 2004
Posts: 556
Location: Berlin - Germany

PostPosted: Thu Oct 05, 2006 4:25 pm    Post subject: Reply with quote

Well, I get along allright with English error messages, although it's not my native language - but I consider localization of portage (as of any other program) a good idea, generally.
And regarding bug reports with localized error messages:
Code:
chris@chemical ~ $ ls -l bogus
ls: bogus: Datei oder Verzeichnis nicht gefunden
chris@chemical ~ $ LC_ALL=C ls -l bogus
ls: bogus: No such file or directory
chris@chemical ~ $

Problem solved, isn't it?
At least I haven't encountered an app yet that doesn't output English messages when run with "LC_ALL=C".

Just my 2 ¤ - cents...
Back to top
View user's profile Send private message
Genone
Retired Dev
Retired Dev


Joined: 14 Mar 2003
Posts: 7742
Location: beyond the rim

PostPosted: Sat Oct 07, 2006 1:57 pm    Post subject: Reply with quote

chrbecke wrote:
And regarding bug reports with localized error messages:
Code:
chris@chemical ~ $ ls -l bogus
ls: bogus: Datei oder Verzeichnis nicht gefunden
chris@chemical ~ $ LC_ALL=C ls -l bogus
ls: bogus: No such file or directory
chris@chemical ~ $

Problem solved, isn't it?

Not really, we would still have to request the english error message. If you mean that portage should force LC_ALL=C internally, this has been debated in the past and while I'd like it some other important people don't like it.
Back to top
View user's profile Send private message
steveL
Veteran
Veteran


Joined: 13 Sep 2006
Posts: 1324
Location: The Peanut Gallery

PostPosted: Sat Nov 03, 2007 3:18 pm    Post subject: Reply with quote

Genone wrote:
Not really, we would still have to request the english error message. If you mean that portage should force LC_ALL=C internally, this has been debated in the past and while I'd like it some other important people don't like it.

I think he meant that a user filing a bug report could easily get the english message by setting LC_ALL=C before running the command. Thus, so long as users with translated strings were educated to do that before filing a bug report, there shouldn't be a major issue.
(Whether the bug-wranglers would agree that such education isn't a major issue, I dunno, but I think people who use translated software are normally aware that English is the defacto language for development.)

Personally, I'd make it output a warning that 'LC_ALL=C emerge blah' should be run before filing a bug report, whenever a fatal error occurs in a non-English locale (which is using translated strings.) Perhaps it could automatically output the english version as well (for fatal errors) if the --verbose flag is in operation (which it normally is when people are troubleshooting.)
Back to top
View user's profile Send private message
Arfrever
Moderator
Moderator


Joined: 29 Apr 2006
Posts: 2359
Location: Polska / Lenkija

PostPosted: Sat Nov 03, 2007 5:22 pm    Post subject: Reply with quote

steveL wrote:
Genone wrote:
Not really, we would still have to request the english error message. If you mean that portage should force LC_ALL=C internally, this has been debated in the past and while I'd like it some other important people don't like it.

I think he meant that a user filing a bug report could easily get the english message by setting LC_ALL=C before running the command. Thus, so long as users with translated strings were educated to do that before filing a bug report, there shouldn't be a major issue.


++

steveL wrote:
Personally, I'd make it output a warning that 'LC_ALL=C emerge blah' should be run before filing a bug report


I think that Bugzilla could recommend using LC_ALL=C before filing a bug report. It would be sufficient.

Perduodu linkėjimus
Arfrever
_________________
Try Subversion 1.7_pre* and Portage 2.3_pre* using Eaedificāta Repository!
Back to top
View user's profile Send private message
steveL
Veteran
Veteran


Joined: 13 Sep 2006
Posts: 1324
Location: The Peanut Gallery

PostPosted: Sun Nov 04, 2007 4:54 am    Post subject: Reply with quote

Arfrever wrote:
I think that Bugzilla could recommend using LC_ALL=C before filing a bug report. It would be sufficient.

Good point. If it were part of the standard header as a small reminder, with a larger one in your face when you report, no-one would have an issue with being picked up on not running it.
Back to top
View user's profile Send private message
seqizz
n00b
n00b


Joined: 14 Jan 2008
Posts: 63
Location: seqizz.net

PostPosted: Thu Aug 28, 2008 4:36 am    Post subject: :\ Reply with quote

I know, i know.. i hate bumps.
An old topic, and everybody thinks different about this.

I'll start to translating man pages to Turkish. But before that one, i've a complete translation patch for *only* emerge --help and emerge --help --verbose outputs. Some information about using emerge bla bla.. Details [link] (turkish)

Particular translations can really confuse users, but don't we need to find a solution?
( :? if this is a problem)

Maybe the information part of the emerge (like man pages and --help, not --info) should be translated, maybe not*.

*On the other hand, using gentoo already needs English (to solve potential problems etc..)
_________________
If there is a wiki, you don't need a brain..
Back to top
View user's profile Send private message
Arfrever
Moderator
Moderator


Joined: 29 Apr 2006
Posts: 2359
Location: Polska / Lenkija

PostPosted: Thu Aug 28, 2008 10:39 am    Post subject: Reply with quote

seqizz wrote:
i've a complete translation patch for *only* emerge --help and emerge --help --verbose outputs. Some information about using emerge bla bla.. Details [link] (turkish)


This is wrong way of translating.
You should use gettext and pygettext.py.
(I still have a patchset which gettextizes some files in Portage.)
_________________
Try Subversion 1.7_pre* and Portage 2.3_pre* using Eaedificāta Repository!
Back to top
View user's profile Send private message
seqizz
n00b
n00b


Joined: 14 Jan 2008
Posts: 63
Location: seqizz.net

PostPosted: Thu Aug 28, 2008 10:55 am    Post subject: :\ Reply with quote

I know my way is so dirty, and not translating actually replacing.
Is gettext default for portage?
Or this will mean nothing.. (Translating over an experimental patch..)
_________________
If there is a wiki, you don't need a brain..
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum