Re: Schema error in 1.3.5 and HEAD

Le dim 06/07/2003 à 10:57, R.I.P. Deaddog a écrit :
> On 2003-07-05(Sat) 00:56:48 +0300, Tommi Komulainen wrote:
> > >         <type>int</type>
> > >         <default></default>
> > 
> > > This is incorrect because a default value can't be empty.. Therefore the
> > > </default></default> line shouldn't be in the schema..
> > 
> > Hmm, is it allowed to leave out the whole default element then?  I
> > couldn't see that explicitly mentioned, only that it may appear below
> > either a <schema> or a <locale> element.
> 
> However it's not quite recommended to let <default> element appear inside
> <locale> element, unless absolutely necessary; translators can often got
> it wrong and translate it into localized string that confuses gconf.
> 
> 
> > > Can I commit this fix on CVS ?
> > 
> > I'm all for it if there's no ill side-effects...  The purpose of that
> > pref is to allow one to override the toolbar style, but by default
> > follow the desktop style.  That's why the default was set to 'NULL'
> > instead of any integer as any given value has only 25% chance of being
> > the desktop default...
> 
> How about adding another integer value that tries to pick up desktop
> default?

We could add '4' for "follow desktop" but it would break old galeon
release..

I've removed <default> in cooker package, with no side effect.

Guys, it is your call..

-- 
Frederic Crozat <[email protected]>
Mandrakesoft



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01