Re: encoding of type_name for e.g. g_register_type_static()

[Stefan Kost <ensonic hora-obscura de>]

Hi Owen,

that is a fair penality ;)

The question is where to put it.
1.) a new para in the longs desc.
2.) as part of the params docs repeated for 
g_type_register_{dynamic|fundamental|static}

Apart the same applies to g_param_specs and signal names.

The brings the old idea of integrating the gobject tutorial into the gobject 
docs ...
If the glib maintainers agree, I apply for a gnome cvs account and prepare that.
IMHO that would provide the most benefit to the docs.

Stefan

> On Sat, 2005-02-05 at 13:32 +0100, Stefan Kost wrote:
>
> > hi hi,
> >
> > I create some g_objects on the fly. The type_name I pass to
> > g_register_type_static(), does this need to adhere to some encoding restrictions
> > (beeing pure ASCII) or is UTF-8 okay?
>
>
> You can find the rules in 
>
>  glib/gobject/gtype.c:check_type_name_I
>
> A doc patch might be appropriate penance for asking on 
> gtk-devel-list :-). (The gobject docs are out-of-line in 
> the tmpl files.)
>
> Regards,
> 						Owen
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> gtk-devel-list mailing list
> gtk-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-devel-list