At 09:12 AM 2003-07-05 -0700, Autrijus Tang wrote:
On Fri, Jul 04, 2003 at 06:14:37PM -0800, Sean M. Burke wrote:
> Oop, one more assumption I'd like to be able to make:
> * Unless a Pod file starts with a BOM, the Pod processor will assume that
> it's in Latin-1 or UTF8, unless/until there's an =e
On Fri, Jul 04, 2003 at 06:14:37PM -0800, Sean M. Burke wrote:
> Oop, one more assumption I'd like to be able to make:
>
> * Unless a Pod file starts with a BOM, the Pod processor will assume that
> it's in Latin-1 or UTF8, unless/until there's an =encoding directive
> seen. So if you're writin
Oop, one more assumption I'd like to be able to make:
* Unless a Pod file starts with a BOM, the Pod processor will assume that
it's in Latin-1 or UTF8, unless/until there's an =encoding directive
seen. So if you're writing a Pod file in any other encoding, you /must/
have an =encoding line.
(I'm CCing the perl-i18n list on this, as this will interest some on the
list; and I may need to pick the brains of a few people on the list.)
So as I'm milling over the implementation and tests for =encoding in
Pod::Simple, I'm starting to settle on some hopefully sane assumptions that
Pod::
