Adriano dos Santos Fernandes wrote:

>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
>

You know vastly more about charsets, collations, and the standard than I
do. I'm just trying to make sure that the pieces fit together.

>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"?
>
>
>
>

That's certainly good enough for starters. If something you like better
presents itself during development, go for it.

But someplace needs to identify the module / entrypoints that contain
the actual code. Does it make sense to have something like

<intl_module my_stuff>
filename $(install)/intl/mystuff
</intl_module>

<charset new_charset>
intl_module my_stuff
...
</charset>