> > Instead, I propose the following glossary
> > entries to define the way in which we're using the terms:
> >
> > plain text
> > Unformatted, human-readable text that consists of a sequence of
> > printable characters in a character encoding such as UTF-8.
> >
> > cleartext
> > Unencrypted data; data that exists in an unprotected, readable format
> > during storage or transmission. Sometimes used as a synonym for
> > plaintext; the input to an encryption algorithm.
>
> Sounds good.  I was trying to make the cleartext entry specify that it is
> generally data which is intended as input to processing, but I wasn't
> particularly successful in creating anything which reads better than what you
> have above.

I've created a V2 patch (attached) including the glossary terms, and
with a verbose commit message as suggested by Laurenz.

> I ran a grep on the docs and found the same occurences. I agree with your 
> changes Karen.

Thank you for the review, Xavier.

And thank you, all, for the helpful discussion and suggestions.

Regards,
--
Karen

Attachment: v2-0001-Doc-standardise-cleartext-and-plain-text-terms.patch
Description: Binary data

Reply via email to