| 1 |
2006-06-22, Xavier Neys sanoi, jotta: |
| 2 |
|
| 3 |
> With a new release coming out soon(-ish), we're going to have to hunt |
| 4 |
> and update quite a few variable data such as snapshot |
| 5 |
> names/locations, CD sizes, kernel versions in all our handbooks. |
| 6 |
> Some time ago, we discussed the possibility of defining values at the |
| 7 |
> beginning of the handbooks so that we need only update each value |
| 8 |
> once, always at the same place. |
| 9 |
|
| 10 |
> If you guys like it, it goes in, but if you think is too complex or |
| 11 |
> too much work to maintain, I shall not push it down your throat :) |
| 12 |
> |
| 13 |
> |
| 14 |
> Feedback welcome, |
| 15 |
|
| 16 |
The change towards variables for version information and such is good |
| 17 |
per se, but as translator I should probably remind, that using |
| 18 |
variables does make creating good translations a bit harder. As an |
| 19 |
example, translation of |
| 20 |
"[...] <keyval id="arch"/> systems and <keyval id="arch"/> |
| 21 |
clones [...]" |
| 22 |
will be "<keyval id="arch"/>-järjestelmät ja <keyval |
| 23 |
id="arch"/>-kloonit" if and only if <keyval/> doesn't contain spaces, |
| 24 |
otherwise hyphens must be preceded by spaces. Variables also |
| 25 |
practically prevent use of any affixes, which will reduce the quality of |
| 26 |
translations in languages with rich morphology, such as Finnish. |
| 27 |
|
| 28 |
So, what I'm basically suggesting is only to avoid overusing these |
| 29 |
variables. While they are mostly fine in version numbers, |
| 30 |
file system paths and such codes, they may cause problems in names, |
| 31 |
phrases and such. |
| 32 |
-- |
| 33 |
Flammie, Gentoo Linux Documentation’s Finnish head translator |
| 34 |
and FlameEyes’ bot <http://dev.gentoo.org/~flammie>. |
Archives