[Zope3-dev] schema initial documentation

[faassen@vet.uu.nl]

On Mon, Apr 22, 2002 at 02:46:02PM +0000, Florent Guillaume wrote:
> This simple example already raises what I believes could be i18n issues:

Agreed.

> - documentation, title: are those only for the programmer? If that
>   is the case, then there is no i18n problem there.

No, these are also used in the user interface, so there is an
internationalisation issue here. We need to figure out which is the
right place to solve this; the schema, the view, elsewhere?
And of course what this solution should look like. :)

> - if there is error checking, then it means the error could possibly
>   get back to the user, so it may be important to have a codification
>   of possible errors to be able to translate them. A simple
>     raise KeyError, name
>   is ok to translate but anything more complex should probably use a new
>   Exception subclass, and they should be part of the schema.

There is validation going on, and the validation errors should definitely be
i18n-aware.

> - date_of_birth: i18n is also probably done at a higher level, but I
>   wanted to mention it also, in case I'm mistaken.

Yes, this issue I've already tackled before in Formulator, so I'm aware
of some of the date-time related issues. Order of year/month/day and such
should I think be handled by the view, but saying that doesn't make it
solved or easy in the new system. :) Formulator just kept all properties 
for each field together, view-dependent or not, but we can't do that with
schema.

I'm glad you've put these issues prominently on our list of things to
think through; thanks!

Regards,

Martijn