Re: [LAD] Ladspa: Text encoding for metadata fields

Thanks Steve. So, now i just need to code a function to convert utf8 to c
strings literals (using 0x82..).

I am developing a functionality to export CLAM networks as ladspa plugins from
the CLAM NetworkEditor interface. It seems to work pretty well now at svn, so
a next step is providing support for LV2 and VST. Any testing, before we make
it fully public, is welcome:
https://iua-share.upf.edu/wikis/clam/index.php/Building_a_LADSPA_plugin

David.

El Friday 01 August 2008 18:16:34 Steve Harris va escriure:
> I think the convention is for UTF-8, but as you say, it was never
> specified. LV2 specifies UTF-8.
>
> - Steve
>
> On 30 Jul 2008, at 20:34, David García Garzón wrote:
> > I have some doubts, as both host and plugin programmer, regarding
> > the text
> > encoding that should be used for Ladspa v1 metadata fields. Is there
> > any
> > convention? Utf8? Is it limited to plain ASCII? Which fields are
> > restricted
> > and which are not?
> >
> > I supose that unicode is supported in some way as many 'makers' have
> > weird
> > signs on their name but the header-documentation does not provide
> > any answer
> > to that.
> >
> > David García Garzón.
> >
> >
> > _______________________________________________
> > Linux-audio-dev mailing list
> > Linux-audio-dev@email-addr-hidden
> > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Sat Aug 2 00:15:02 2008