-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/13/2016 08:08 AM, Fernando Rodriguez wrote:
> On 07/11/2016 12:11 AM, P Levine wrote:
>> Glep 31 states that text files in the portage tree should use UTF-8
> encoding. I see nothing indicating any standard encoding for files in
> the /etc/portage directory. Since everything I have seen in portage's
> python source-code seems to imply Unicode as valid but I can see nothing
> specific to UTF-8, I thought I'd ask.  Is there any official Gentoo standard
> documentation that defines the acceptable set of character encodings for files
> in /etc/portage?
> 
> I just glanced over Glep 31 and it does not say that. It is talking about
> ChangeLogs and metadata.xml (because they contain developer names with unicode
> characters). For patches and such it says to follow upstream suit.
> 
> If you try to use non-ASCII characters on ebuilds repoman will whine so I
> suppose only ascii is supported and likewise there's nothing that I know of on
> /etc/portage that requires non ascii characters.
> 
> 
Actually, it does says it, my bad. But repoman does complains if you use 
non-ASCII
characters and it says not to print non-ASCII so I guess it's talking about 
comments.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXhjCoAAoJEPbOFX/5UlwcFzMP/RUKDiN5Svo8HQAzVm0GxZKd
Mf9tIpDQUiUl+ZudSEVcpB8YdM5mcFY/a2VMLTjanppi6NLdQlDywIOWET7e8uSs
X4qR0D2bxDDs8TtM1aiWSa5EzeJ42eNIN/qLFAImWDluZFNxokXt78aaEX5O1o+u
dYsygCnMzjRFc0y9JxoZpYWKq7tehHdBzxgeOHEzcu0m5DXxqoHWFxkqu1mr5Hjz
lTe91gLsDTmqlttlqCGaac0NZMXZHh1SVtysJBlhryTOMWu/Xh1YQDP6SXX4Mnwi
BvsSMXF4FrMvMaSxnn56DHDssR3fRFx595+DrU26GtNgTdBpmE24ymjsdcSm9Hm9
ovnG0h8Qys+pB15VUioNdR3LZTHMAO2/mx6lMYRdKvv735DEbIwCEXanSB9CG+nI
VpOPaiYGunzDfsnV03ZRVFutbABM+cK70rBQeLUtH5FllDq9g3xEIMpdkradqRXC
uXQTIoFslJxZH/AXGQTFCmIr6RGHdVfmmuHvp+NWGbwy3Q1DOfjcJK533lSoYScZ
8q2FDYdwidTDSCX1TaR5WKMpiwSdVftie9VOyotklk/MVukxHGmi8PH3guYqC3M5
ksy7AA0UrKXDiEaiVoMXNcP3FtJdWC6q+7a8PH59QOPDbZySP/HscGC7raFEMgNv
JZ2NVoGuWXvwJMmJh2x9
=f29Q
-----END PGP SIGNATURE-----

Reply via email to