From: Jakub Narebski <jnareb@gmail.com>
To: "Jérémie NIKAES" <jeremie.nikaes@gmail.com>
Cc: thomas@xteddy.org, git@vger.kernel.org,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: Git-mediawiki : Encoding problems in perl
Date: Wed, 08 Jun 2011 10:04:17 -0700 (PDT) [thread overview]
Message-ID: <m3y61cdzmi.fsf@localhost.localdomain> (raw)
In-Reply-To: <BANLkTimy85b3nu05FBjXzdnTJP0RBWdxiQ@mail.gmail.com>
Jérémie NIKAES <jeremie.nikaes@gmail.com> writes:
> While working on the git-mediawiki project[1], we ran into some
> problems regarding utf8 encoding of files. Most of them have been
> solved, however, one is still pretty annoying.
> Let me illustrate it :
>
> I want to edit a page on mediawiki using the API, with a very simple example :
>
> my $mw = MediaWiki::API->new();
> $mw->edit( {
> action => 'edit',
> title => 'Main_page',
> text => 'été',
> } ) ;
>
> But, when I look at the page on mediawiki, I see weird characters : été.
Take a look at
http://stackoverflow.com/questions/6162484/why-does-modern-perl-avoid-utf-8-by-default
especially accepted answer.
In short (I don't agree with everything there, and not everything is
needed for all but extremal Unicode usage): if your script is written
using UTF-8 like in above examples, use
use utf8;
If this is simplification, and this text comes from other file or is
result of output of some command, use
use utf8::all;
or take a look what it does and put relevant parts in your script.
> I tried text => encode_utf8('été') with no success.
>
> This makes pushing changes from git to mediawiki buggy since pulling a
> file with accentuated characters and pushing it right after changes
> things on the wiki.
>
> While googling (a lot), I found that utf8 was pretty tricky in perl...
> The only thing that seems to solve things is a simple addition of 'use
> encoding utf8' at the top of our script.
> However
> A) Adding this line requires that I remove 'use strict;'
use encoding ':utf8';
or
use encoding 'utf8';
> B) I found some information about this pragma encoding and it seems to
> be unadvised to use it
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-06-08 17:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 13:45 Git-mediawiki : Encoding problems in perl Jérémie NIKAES
2011-06-08 14:37 ` Steffen Daode Nurpmeso
2011-06-08 15:01 ` Jeff King
2011-06-08 15:37 ` Matthieu Moy
2011-06-08 15:45 ` Jeff King
2011-06-08 15:46 ` Jérémie NIKAES
2011-06-08 15:58 ` Matthieu Moy
2011-06-08 16:15 ` Jérémie NIKAES
2011-06-08 16:18 ` Jeff King
2011-06-08 16:26 ` Jérémie NIKAES
2011-06-08 16:27 ` Matthieu Moy
2011-06-08 16:30 ` Jérémie NIKAES
2011-06-08 17:07 ` Jakub Narebski
2011-06-08 17:11 ` Matthieu Moy
2011-06-08 18:03 ` Jérémie NIKAES
2011-06-08 18:20 ` Matthieu Moy
2011-06-08 21:51 ` Jeff King
2011-06-08 22:36 ` Jérémie NIKAES
2011-06-08 17:04 ` Jakub Narebski [this message]
2011-06-08 17:59 ` Jérémie NIKAES
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y61cdzmi.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jeremie.nikaes@gmail.com \
--cc=thomas@xteddy.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).