Re: Content string encoding?
- From: Alexander Larsson <alexl redhat com>
- To: Murray Cumming <murrayc murrayc com>
- Cc: gnome-vfs-list gnome org, Jonathon Jongsma <jonathon quotidian org>
- Subject: Re: Content string encoding?
- Date: Mon, 04 Feb 2008 15:41:06 +0100
On Fri, 2008-02-01 at 17:36 +0100, Murray Cumming wrote:
> On Fri, 2008-02-01 at 09:54 +0100, Alexander Larsson wrote:
> > On Fri, 2008-02-01 at 01:01 +0100, Murray Cumming wrote:
> > > We are wrapping the g_content_type_* functions for giomm, and have a
> > > question:
> > >
> > > Can/must the content strings here be UTF-8, or are they a blob of data
> > > of unknown encoding (a bit like a URI)
> > > http://library.gnome.org/devel/gio/unstable/gio-GContentType.html
> >
> > I'm not sure. I mean, on unix they are mimetypes, and on windows they
> > are extension strings like ".doc", "audio", "*". Both of these will in
> > practice be ASCII strings in all cases, but I don't think there is
> > anything prohibiting e.g. adding a non-ascii type in the windows
> > registry which then could be returned to the app via gio.
>
> Could that mean that they are ever some odd encoding such as UCS2, which
> would not be UTF-8?
Actually, looking at the win32 the registry is stored in unicode and we
always convert to UTF-8 in libgio.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]