Jim Starkey wrote:

>
>
> Adriano dos Santos Fernandes wrote:
>
>
>>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
>>
>>
>
> Do you have reason why this should be a totally different format from
> everything else in the system?
>
> We should have a single meta-syntax for configuration information.

I only want to say that plugin can implement:
- one collation but not the charset used for the collation
- one collation that can be used for different charsets
- each plugin has one manifest

In this example a external plugin define only custom_unicode_collation but not utf8 and utf16 charsets and define a new charset:

<charset utf8>
charsetImplemented no
collation custom_unicode_collation
</charsets>

<charset utf16>
charsetImplemented no
collation custom_unicode_collation
</charsets>

<charset new_charset>
charsetImplemented yes
</charsets>

Do you have a better way about this "charsetImplemented"?


Adriano