Bug#246016: Define allowed charsets properly
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Barth <aba@not.so.argh.org> writes:
> Is this ok for you all?
I think it's fine. WRT requiring a transcription of "non-Latin"
characters, I think there should be some sensible
guideline/restriction on the amount of non-Latin text allowed. For
example, a few words would be OK, but several paragraphs would not
(that's what localisation is for). This will depend on the context of
why the non-Latin characters are required, but I think clarifying what
should be allowed would be a good idea.
For non-character non-ASCII symbols, I think there may be cases where
these could be used usefully, but it might be a good idea to suggest
that they are used in moderation until they are available with all the
common fonts. i.e. ASCII equivalents should be used if at all
possible. This is purely pragmatic--until we are fully supporting
Unicode everywhere, we should make reading text files with existing
tools/terminals/fonts as easy as possible.
Regards,
Roger
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFAjr1sVcFcaSW/uEgRAtnBAJ9iOG9inalCCl70QdPDD6hLzNpGvACgt0pE
J+3khfiAn9LecRf2eZ2APiA=
=Ymb4
-----END PGP SIGNATURE-----
Reply to: