Hi,

On Sat, 14 Jul 2001 00:27, Marcus Crafter wrote:
> Hi Neeme,
>
>       Hope all is well!
>
>       I've had an interesting discussion with a fellow cocoon developer
>       about the format of the message catalogue files. He made an
>       interesting point below. I'm interested in your opinion as well.
>
> > Response:
> > > Marcus Crafter wrote:
> > >
> > > ....
> > >
> > > 2. Format of the catalogue files - what should it be ? Currently I
> > > have specified a prototypical format. Basically it's:
> > >
> > > <?xml version="1.0"?>
> > > <messages>
> > > <key>text</key>
> > > </messages>
> > >
> > > Anyone have any further thoughts there ?
> >
> > Speaking frankly, I prefer something like the old format (not necessary
> > the tag names, but the structure):
> >
> > <messages locale="en">
> >   <message key="Key_value">The key translations</message>
> > </messages>
> >
> > This format can be formalized with a schema or a DTD and you can check
> > the correctness of the dictionary/catalogue before using. Also, I think,
> > that this format can be easily transformed to another one because the
> > structure is definite. In your version of dictionary the DTD depends on
> > the content of the page and it's not very convenient and cannot be
> > controlled.
>
>       What are your thoughts ? suggestions ?

I don't use the code but I do like the change from what I understand ;)
One thing though. When we move excalibur to new CVS can we promote i18n stuff 
out of scratchpad? It seems like a good idea but as I don't use it ...

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to