Re: [BUG] Blank about dialog box - does everyone have a funcional iconv ?

On Fri, 11 May 2007 20:00:51 +1000
<tpgww@xxxxxxxxxxx> wrote:

> > Here BUILDSTAMP is in current locale encoding (which is KOI8-R in my case).
> > While other strings will be converted to UTF-8 by gettext. So BUILDSTAMP
> > and BUILDDATE should be converted to UTF-8 too, prior to go to 
> > g_strdup_printf.
> > This can be done either at buildtime, like this:
> > 
> > --- emelfm2-devel/Makefile.orig     2007-05-10 19:19:13.000000000 +0400
> > +++ emelfm2-devel/Makefile  2007-05-10 19:19:06.000000000 +0400
> > @@ -48,8 +48,8 @@
> >  RELEASE=
> >  #RELEASE=.1
> >  PROGNAME=emelFM2
> > -TIMESTAMP=$(shell date +"%02d %b %04Y")
> > -DATE=$(shell date)
> > +TIMESTAMP=$(shell date +"%02d %b %04Y" | iconv -t utf-8)
> > +DATE=$(shell date | iconv -t utf-8)
> >  INFO=$(shell uname) $(shell uname -r)/$(shell uname -m)
> >  COPYRIGHT=2003-$(shell date +"%04Y"), tooar <tooar@xxxxxxx>
> >  OPSY := $(shell uname)
> > 
> > Or at runtime, using iconv.
> Do all OS's that support gtk (or more particularly, upon which emelfm2 might
> be built for use with gtk) also have a functional iconv utility on hand, by
> default ? I thought I read somewhere that this is not so ??
I do not know exactly. But I think that there might be a system without
iconv command. So that strings should be converted to UTF-8 at runtime,
after all emelfm2 already uses convertion functionality from glib.

> I suppose that any "make" argument that may be supplied on a shell command
> line, and those arguments' derivatives (paths derived from PREFIX, document
> names) also needs conversion, potentially.
Well, in build.h I found only two strings - BUILDSTAMP and BUILDDATE. It is
unlikely that someone wants to set PREFIX or *_DIR in encoding other then ASCII.


-- 
Alexander Orlov


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: