| 1 |
2006-06-10, Diego 'Flameeyes' Pettenò sanoi, jotta: |
| 2 |
|
| 3 |
> I'm actually going to work to add to Portage (will-be-2.2) i18n |
| 4 |
> capabilities next week, and I'll be doing for sure the Italian |
| 5 |
> translation. |
| 6 |
|
| 7 |
Would this be a fix to Portage NLS bug |
| 8 |
<http://bugs.gentoo.org/show_bug.cgi?id=13618>? If so, have you |
| 9 |
considered what I have said in the bug? If the translation possibility |
| 10 |
is going to concern the static Portage messages only, I fear that it |
| 11 |
will be slight waste of time. Users will generally find partial |
| 12 |
translations more harmful than no translations at all, and in Portage's |
| 13 |
case I think that the ebuild/eclass messages will often contain the more |
| 14 |
important parts of information, which will surely cause more annoyance |
| 15 |
than be useful. Imagine that for fetch restrictions, you get first |
| 16 |
generic note about fetch restriction in your native language, then n+1 |
| 17 |
lines of lengthy information how to fetch in English, not nice. |
| 18 |
Similarly for post package install instructions, or conflicting USE |
| 19 |
flag instructions etc. etc. |
| 20 |
|
| 21 |
-- |
| 22 |
Flammie, Gentoo Linux Documentation’s Finnish head translator |
| 23 |
and FlameEyes’ bot <http://dev.gentoo.org/~flammie>. |
Archives