| From Benjamin Drung <
[hidden email]>
| Sat, 17 Oct 2009 23:15:34 +0200
| Subject: [Audacity-devel] Compilation error in AboutDialog.cpp
> Am Samstag, den 17.10.2009, 22:11 +0100 schrieb Gale Andrews:
> > | From Richard Ash <
[hidden email]>
> > | Sat, 17 Oct 2009 21:45:30 +0100
> > | Subject: [Audacity-devel] Compilation error in AboutDialog.cpp
> > > On Sat, 2009-10-17 at 21:19 +0100, Gale Andrews wrote:
> > > > | From Al Dimond <
[hidden email]>
> > > > | Sat, 17 Oct 2009 10:29:57 -0600
> > > > | Subject: [Audacity-devel] Compilation error in AboutDialog.cpp
> > > > > Just cvs up'd this morning and got a strange compilation error.
> > > > >
> > > > > AboutDialog.cpp:100: error: converting to execution character set: Invalid or
> > > > > incomplete multibyte or wide character
> > > > >
> > > > > The line was for André Pinto's name, and I assume the é was the character it
> > > > > was complaining about. I think the issue is that GCC (on my computer) was
> > > > > assuming UTF-8 and the file is actually ISO8859-something.
> > > > >
> > > > > I got it to compile and work correctly on my system in two different ways.
> > > > > First, adding "-finput-charset=iso8859-1" to CXXFLAGS in src/Makefile (I know
> > > > > that's not suitable for anything real, but I don't know exactly how all the
> > > > > autotools stuff works). Second, changing the "é" to "\u00e9" in the source
> > > > > file. I'm not sure what's the preferred method for doing this sort of thing,
> > > > > though I'd guess the second is, because every compiler should be able to
> > > > > handle it.
> > > >
> > > > Thanks Al. I had updated the About Dialog and I wondered
> > > > if é might cause some issue with GCC (it doesn't with Visual
> > > > Studio). I get the same issue compiling on Ubuntu.
> > > >
> > > > I did wonder about using the HTML equivalent instead
> > > > (é) as per:
> > > >
http://www.alanwood.net/demos/ansi.html> > > >
> > > > Unless someone wants to do differently or beats me to it
> > > > I'll commit the change to \u00e9 which compiles for me
> > > > on both Windows and Linux.
> > >
> > > Why don't we convert the file to UTF-8, then both compilers should
> > > accept it (at least, GCC will, and I'm told VS will) with the character
> > > in it?
> >
> > I could convert to UTF-8 in either TextPad or Notepad++.
> > The latter gives an additional option to convert to "UTF8
> > with BOM":
> >
http://en.wikipedia.org/wiki/Byte-order_mark> >
> > Is either preferable?
>
> The BOM-less version is preferred.
I misread that menu in Notepad++, the options are actually "Convert
to UTF8" and "Convert to UTF8 without BOM". I used the latter, but
although it compiles on both Linux and Windows fine, on Windows
the "é" displays in the dialogue as " é", as it would if you read an
.aup file in a text editor that can't read UTF-8. Same result with
onverting to UTF "with BOM", so I gave up and committed the "é" as
"\u00e9" in a normal ANSI file.
Gale
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
