| 1 |
On Sat, 3 Dec 2011 22:14:16 -0800 |
| 2 |
Alec Warner <antarus@g.o> wrote: |
| 3 |
|
| 4 |
> Can we just translate the error messages? |
| 5 |
|
| 6 |
*I* sure can but it takes time and effort, and for ever developer who |
| 7 |
looks at this, the process is repeated unless bug wranglers or other |
| 8 |
handy users happen to provide the translation. |
| 9 |
|
| 10 |
Just think of looking into a large build log, checking that the |
| 11 |
"error:" should now be "Fehler:" or something in an altogether |
| 12 |
different script you can't even read, and then searching backwards |
| 13 |
through the log to find the first occurrence. Do the same for "No such |
| 14 |
file or directory", "undefined reference" and so on - the things that |
| 15 |
most commonly get translated. |
| 16 |
|
| 17 |
Or do you mean automate translation whenever something is attached to a |
| 18 |
bug report? I think we'd be doing things the wrong way round then, but |
| 19 |
feel free to donate the machine translation server farm to do it. Also, |
| 20 |
make sure the result uses the same (original) strings and that you don't |
| 21 |
get funny "google translate" surprises. |
| 22 |
|
| 23 |
|
| 24 |
jer |
Archives