| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Harald van Dijk yazmış: |
| 5 |
> On Sun, Mar 08, 2009 at 09:27:20PM +0100, Alexis Ballier wrote: |
| 6 |
>> Moreover this would automagically solve the [a-z] & friends regexp |
| 7 |
>> failures; though that's still good QA to fix them but we wouldn't |
| 8 |
>> encounter them anymore. |
| 9 |
> |
| 10 |
> We would encounter them when using the programs outside of portage, but |
| 11 |
> not when running the testsuite (if available) from within portage. It |
| 12 |
> would succeed in working around compile-time only bugs, but it would be |
| 13 |
> a major pain for locale bugs that can also cause problems at run time. |
| 14 |
> |
| 15 |
> |
| 16 |
I agree. There are quite a number of bugs, either compile time or |
| 17 |
runtime, that can be spotted and reported to upstream (and hope that |
| 18 |
they get fixed) in Turkish locale and I posted on my dev blog why[1] |
| 19 |
this happens. I choose to translate the messages after the build.log if |
| 20 |
I reproduce the bug only in Turkish locale. If our bug reporting guide |
| 21 |
is not guiding people (yeah people don't read docs and especially ones |
| 22 |
that are longer than a paragraph and in a language that they can't read) |
| 23 |
portage could say a few words on sending the bug report in English if it |
| 24 |
spots another locale with the exception of the bug being a locale |
| 25 |
specific issue. |
| 26 |
|
| 27 |
1: |
| 28 |
http://blogs.gentoo.org/serkan/2008/11/16/applications_failing_with_turkish_locale |
| 29 |
- -- |
| 30 |
Sincerely, |
| 31 |
Serkan KABA |
| 32 |
Gentoo Developer |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 35 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 36 |
|
| 37 |
iEYEARECAAYFAkm0kPgACgkQRh6X64ivZaKsKgCfYPtokmwM6G1jyBM1tbBZOrc5 |
| 38 |
RVwAnAwkHu+nIN4Khtj0lZYgSRnjKiMC |
| 39 |
=9n5G |
| 40 |
-----END PGP SIGNATURE----- |
Archives