Fwd: Re: JobViewServer specification proposal

[Rafael Fernández López]

(Oops, this mail should have gone to xdg, not only to Aaron)

Hi all,

> that seems like quite a bit of hassle and coordination just to add a new
> unit type, and honestly it isn't that hard to think of new ones.
> additionally, what do we do about units that only one application would
> ever use? ignore it or bloat the spec?

In theory if an application needs a new string (note that in that parameter 
you dont pass a i18n string, but a plain string, 
aka "bytes", "files", "dirs") it should ask us for being added to the spec.

However I really agree this is for sure not the best solution. What other 
alternatives we have assuring that they are cross-desktop ?

> how are unknown units dealt with in 
> between spec updates or on older systems?

I haven't thought of this...

> i take it that this is about i18n and consistent display of labels,
> correct?

Yes, that's correct.

> i think having common types available is good, but there ought to be a
> "good enough" fallback for adding random new units by doing the translation
> for these on the client side somehow.

Agreed. But I have the same practical question, how can we do a safe fallback 
making the application compatible with new types or with newer versions.

All I can think about is to pass the string internationalized, but I don't 
know exactly how.


Regards,
Rafael Fernández López

GPG Fingerprint: B9F4 4730 43F8 FFDD CC5E BA8E 724E 406E 3F01 D070
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/xdg/attachments/20080409/c3854c88/attachment.pgp