Lines Matching full:but

15 is actually a generic C<Encode> tutorial and C<Encode> FAQ. But many people
27 Well, if you can, upgrade to the most recent, but certainly C<5.8.1> or newer.
62 positive, but it's best to avoid it.
88 because UTF-8 is usually the encoding you wanted! But don't be lazy, and don't
109 Some database drivers for DBI can also automatically encode and decode, but
133 identifiers (but they still have to be "word characters" according to C<\w>),
144 encoding as long as it can. (But perhaps originally it was internally encoded
164 Perl assumes that the program is prepared to deal with Unicode, but when
186 You can't. Some use the UTF8 flag for this, but that's misuse, and makes well
270 machine, the source code does not change, but the STDIO environment might.
285 widely accepted as good behavior when you're writing, but it can be dangerous
291 but this is considered bad style. Especially C<_utf8_on> can be dangerous, for
310 9999999, but if you encode that to UTF-8, you get a substitution character (by
320 format being any specific encoding. But since you asked: by default, the
326 encoding for a certain string is, but instead just encode it into the encoding