270702 - Proper Dutch translation for decrypt

Status: RESOLVED FIXED

(Mozilla Localizations :: nl / Dutch, defect)

Description

[u81239]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.7.5) Gecko/20041107 Firefox/1.0

We still haven't really resolved the issue with 'encrypt' and 'decrypt'... The
common Dutch translation for encrypt is 'versleutelen', however the translation
of decrypt is unclear.

Whatever we choose needs to be applied consistently throughout the entirity of
Firefox. Especially in the glossary.xhtml (and glossary.rdf) Help files this
terminology is used a lot.

I have seen 'ontsleutelen' used a few times on the internet but not often (I
think its use is usually avoided). 'Ontcijferen' is closer but doesn't match
with 'versleutelen' (and its opposite 'vercijferen' is just weird).

So I see a few options:
Versleutelen - Ontcijferen
Versleutelen - Ontsleutelen
Coderen - Decoderen

In the last case we would when necessary use 'coderen' instead of (or together
with) versleutelen.

Maybe someone has another suggestion? Opinions please?


~Grauw

Reproducible: Always
Steps to Reproduce:

Comment 1

[Barend]

I would choose 'coderen' / 'decoderen'. It reflects the meaning of 'encrypt'
/'decrypt' well. I have no other suggestions.

Comment 2

[u81239]

Of course using 'codering' for this purpose conflicts with 'encoding' (as-in
character set)... Question is, is that a problem? I'd say if we use 'coderen'
and 'decoderen' in the context of encryption, we should expressly use it in
combination with 'versleutelen'.

New suggestion:
Versleutelen & versleuteling decoderen ?


~Grauw

Comment 3

[Frank]

I like the suggestion of martijn (mozbrowser) to use "beveilingd" en
"niet-beveiligd". I know it is not the 100% translation, but "het dek de lading"
which is more important.

And rememeber that "coderen" is not the same as "beveiligen/versleuten". ASCII
and UTF-8 are types of coding and not encryption.

Comment 4

[u81239]

Frank: yes, we are using 'beveiligd' whenever possible. However 'encrypt' does
not translate directly to 'beveiligd' and decrypt does not translate *at all* to
'niet-beveiligd'. Often, the context requires us to be more specific than just
saying 'beveiligd'. In those cases, there is no problem to use 'versleuteld',
except that whenever 'decrypt' is used that poses a bit of a problem (hence this
bug :)).

I know 'coderen' isn't a direct translation of 'encrypt'. If it were, there
wouldn't be a problem ^_^. Encryption is a type of encoding though. So I think
when you use it in combination with 'versleuteling' as in my last suggestion
(which I like) it would be ok.

Comment 5

[Martijn Ras]

Characterset encoding has been consistently translated as tekenset.

This page might be helpful:
http://www.vandale.nl/opzoeken/woordenboek/?zoekwoord=code

Notice code meaning:
1 stelsel van signalen met behulp waarvan een bepaalde informatie wordt overgebracht
2 geheimschrift

Coderen and decoderen are the best option, we can not use 'beveiligd' here for
that's used to translate "secure".

Comment 6

[Martijn Ras]

Later over beslissen ...

Comment 7

[u81239]

In the Help files I have reviewed so far, I have used 'versleutelen' vs.
'decoderen'. Maybe not perfect but it's better than what we have now :).
Changing 'versleutelen' into 'coderen' depending on the outcome of this bug
should be easy.

Comment 8

[Frank]

Shouldn't this bug be closed?

Comment 9

[u81239]

I don't see a solid decision yet...

Comment 10

[Hendrik Maryns]

Ik voel meer voor vercijferen vs. ontcijferen.  Het eerste is weliswaar niet
zeer gangbaar, maar de betekenis is duidelijk, zeker als het in combinatie met
ontcijferen gebruikt wordt.
Schiet me niet dood, maar ik zie geen reden hier Engels te gebruiken, het is
toch voor Nederlandstaligen bedoeld!

Comment 11

[Tim Maks van den Broek [:mad_maks]]

volgens mij kan deze bug gesloten worden