> However, combining Jon Gorman's recommendation with some Googling, I get:
>
> my $outfile='4788022.edited.bib';
> open (my $output_marc, '>', $outfile) or die "Couldn't open file $!" ;
> binmode($output_marc, ':utf8');
>
> The open statement may not be quite correct, as I am not familiar with t
> You can set the correct encoding succinctly on opening files
> e.g. open my $fh, '>:encoding(UTF-8)', $outfile
You might also see this even more succinct variant:
open my $fh, '>:utf8', $outfile
though technically speaking, that will not give you guaranteed conformant UTF-8
because it could
rl4lib@perl.org
Subject: RE: Opening & writing to UTF-8 files; copyright symbol again --
solution
Hey, that’s my post! Anyways, I haven’t really looked into what your problem
is, but when you said that the copyright character is getting transformed to A9
even though it is supposedly stored a
On Fri, Nov 13, 2015 at 10:05:01PM +, Highsmith, Anne L wrote:
> I should probably say, "apparent solution" 'cause character set issues never
> seem to end.
>
> However, combining Jon Gorman's recommendation with some Googling, I get:
>
> my $outfile='4788022.edited.bib';
> open (my $output_
Hey, that’s my post! Anyways, I haven’t really looked into what your problem
is, but when you said that the copyright character is getting transformed to A9
even though it is supposedly stored as C2 A9 in the database, it made me think
of how there can be two UTF-8 representations for the same c
