Bytes in the source text that have their high-bit set will be treated
as being part of a literal UTF-8 character. This includes most
-literals such as identifiers, string constants, constant regular
-expression patterns and package names. On EBCDIC platforms characters
-in the Latin 1 character set are treated as being part of a literal
-UTF-EBCDIC character.
+literals such as identifier names, string constants, and constant
+regular expression patterns.
+
+On EBCDIC platforms characters in the Latin 1 character set are
+treated as being part of a literal UTF-EBCDIC character.
=back
and utf8::downgrade are always available, without a C<require utf8>
statement-- this may change in future releases.
+=head1 BUGS
+
+One can have Unicode in identifier names, but not in package/class or
+subroutine names. While some limited functionality towards this does
+exist as of Perl 5.8.0, that is more accidental than designed; use of
+Unicode for the said purposes is unsupported.
+
+One reason of this unfinishedness is its (currently) inherent
+unportability: since both package names and subroutine names may need
+to be mapped to file and directory names, the Unicode capability of
+the filesystem becomes important-- and there unfortunately aren't
+portable answers.
+
=head1 SEE ALSO
L<perlunicode>, L<bytes>