[vertaling] Untranslated strings in GRUB Dutch translation

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 02.03.2012 20:05, Benno Schulenberg wrote:
> Hello Vladimir,
>
> On Fri, Mar 2, 2012, at 14:10, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> Hello, all. Thank you very much for grub Dutch translation. When I was
>> discussing with German team it turned out that the msgstr's in grub.pot
>> weren't clear enough. Was it the same problem for Dutch translations as
>> well?
> Some of the strings were indeed hard to understand, so the recent and the
> additional clarifications were and are helpful.  But the main reason not all
> strings are translated to Dutch yet is: lack of time.
No problem, I was mainly looking for feedback on msgids in order to 
improve them.
>    And sometimes I can't
> find the right wording/phrasing in Dutch, so I leave the string fuzzy, telling
> me I have to look at it further.
I understand that. With non-Germanic languages it can be even more 
difficult.
>> I've fixed, at least some of them. Updated pot is at
>> http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.pot
>> If you think that clarification are good enough, I submit it to TP.
> The clarifications are okay.  Just one thing: please start with a capital letter
> after the "TRANSLATORS:" tag -- the tag isn't really part of the sentence,
> so the real sentence should start with an uppercase letter.
Added this to my todo.
>
> And there's a closing quote missing in:
> #. TRANSLATORS: "TARGET" as in "target platform
Fixed, thanks.
>> msgid "Leaf virtual device (file or disk)"
>> msgstr "Blad virtueel apparaat (bestand of schijf)"
> Yes, this one could use some clarification.  What is a "leaf virtual device"?
I've added following comment:
       /* TRANSLATORS: The virtual devices form a tree (in graph-theoretical
      sense). The nodes like mirror or raidz have children: member devices.
      The "real" devices which actually store data are called "leafs"
      (again borrowed from graph theory) and can be either disks
      (or partitions) or files.  */
>> msgid "Invoke user configuration routing."
>> msgstr "(doet momenteel niets)"
> As far as I can tell, user configuration routing does not work yet in BSD,
> so this option does nothing (yet) I think, and I've translated it as such,
> but left it fuzzy.
I've kinda wondered why fuzzy matching would put it there.
The problem is that the options are parsed and therefore documented in 
GRUB but the result is just some bits changed in a variable passed to 
kernel. So you can easily make "-s" map to "explode this computer" (but 
you'll need to put some explosive peripheral first and write a driver). 
Some of the options may be either leftovers or available only on some 
specific builds. Former is especially likely for FreeBSD (this option is 
from it) since it now prefers environment variables for communication 
between bootloader and kernel. I don't think that removing of obsolete 
options is a good idea since it is still possible to boot an obsolete OS 
in GRUB and sometimes having an obsolete system around may be the only 
way to solve some specific tasks. I should probably mention this in 
manual but a short help is probably not a place to explain why some 
options don't work anymore.

I'll fix few bugs and will make a new pre-release /TP upload this weekend.

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko