Jim Starkey wrote:

> Samofatov, Nickolay wrote:
>
>
>>Jim,
>>
>>
>>
>>>Is the manifest file a known format? If so, where can I find
>>>the definition?
>>>
>>>
>>
>>The format is not yet known for Firebird, but is meant to be something
>>very simple describing contents of something else. Traditional manifests
>>on UNIX and Windows are usually XML files, but something like this will
>>do either:
>>
>>==============
>># Comment
>>
>>Charsets:
>>GB2311
>>WIN1251
>>
>>Collations:
>>PT_BR
>>PWX_CYRL
>>==============
>>
>>
>>
>>
>
> Rather than inventing yet another configuration file format, why not use
> the Vulcan meta-syntax? The code is there for the taking, the interface
> is trivial, and it would provide a smooth upgrade path. Something like
> this:
>
> <charset GB2311>
> filename $(install)/intl/yada
> collation pt_br
> </charset>
>

I think this don't fit well.

For easy plugin installation, each plugin (library) need one manifest file.
If plugin implement one collation don't necessary mean that it implement the charset.

I think should be something like this:

[charsets]
win1251
win1252
iso8859_1

[collations]
win1252:win_ptbr
iso8859_1:pt_br
other_charset:some_collation


Adriano