Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
Set by moderator on 21 August 2017.
01:52 ilbot3 joined
moderator Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
03:52 llfourn joined 06:59 domidumont joined 07:07 domidumont joined 07:28 domidumont joined
nine A rather simple alternative to Punycode could be URL encoding of non-ASCII characters. Easy to implement, fast and compatible. 08:09
09:00 samcv joined 09:43 lizmat joined 10:40 leont joined 11:26 leont joined 12:46 lizmat joined 12:47 domidumont joined, leont joined
domidumont nine: punycode can encode any unicode character. URL encoding is limited to special US ascii chars. 12:55
nine domidumont: one can URL encode all UTF-8 encoded characters 12:56
domidumont how ? 12:59
nine domidumont: en.wikipedia.org/wiki/Percent-enco...trary_data 13:01
domidumont hmm, ok.. 13:30
leont punicode is for dealing with domain names 13:33
Those are highly restricted indeed
[<[0..9a..z-]>+\\.]+ I think 13:35
nine Pretty much, yes. Whereas percent encoding was created for pathy things 13:37
13:58 domidumont joined 14:23 lizmat joined 15:22 domidumont joined 15:44 lizmat_ joined 16:21 lizmat joined 16:33 domidumont joined 17:26 stmuk_ joined 19:06 domidumont joined
ugexe yeah. we need an encoding that prioritizes the encoding of :: to the most sane thing 20:09
oh I guess not if you root them in a sha1 prefix folder (and not a folder with the dist name encoded with this) that is irrelevant 20:11