Front page | perl.perl5.porters |
Postings from May 2003
From: Dan Kogai
May 25, 2003 09:31
Message ID: 5DD41882-8ECE-11D7-B53B-000393AE4244@dan.co.jp
Isn't it possible that we add another directive to specify encoding?
Though pod2man still has some problem handling non ISO-8859-1 text,
HTML has no problem and there is no reason you cannot read
international POD documents via http://search.cpan.org/ so long as
charset= is set correctly (so far search.cpan.org uses ISO-8859-1 for
no-matter-what basis. Those pages with UTF-8 texts are handled by
character entities such as the name of AUTRIJUS).
To prove my point, see this page.
You see line noise? But try the following URL to convert it.
You may not understand what it says but it should now good on UTF-8
If you are interested in the source of my charset.cgi, try
So all you need is the ability to specify encoding. No other tricks
like transcoding is necessary.
(Well, besides that, for search.cpan.org in particular, it is a BAD
idea to use character entities besides '<>&"' exactly because of that).
Therefore I suggest something like
so POD parser can see it and generate something like.
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
and make this directive effective till the next occurance of =encoding
so you can go like
Dan Kogai <email@example.com>
小飼 弾 <firstname.lastname@example.org>
In the same document.
Dan the Man with Too Many Languages to Work with