Kalle Olavi Niemitalo <[EMAIL PROTECTED]> wrote Sat, Aug 05, 2006:
> +unicode_val_T
> +unicode_fold_label_case(unicode_val_T c)
> +{
> +#if __STDC_ISO_10646__ && HAVE_WCTYPE_H
> + return towlower(c);
> +#else /* !(__STDC_ISO_10646__ && HAVE_WCTYPE_H) */
> + /* For now, this supports only ASCII. It would be possible to
> + * use code generated from CaseFolding.txt of Unicode if the
> + * acknowledgements required by http://www.unicode.org/copyright.html
> + * were added to associated documentation of ELinks. */
> + if (c >= 0x41 && c <= 0x5A)
> + return c + 0x20;
> + else
> + return c;
> +#endif /* !(__STDC_ISO_10646__ && HAVE_WCTYPE_H) */
> +}
We already have derivative work of the Unicode SGML entity table.
So adding this to the documentation should be done anyway.
Scrool and I talked about using UCData for handling Unicode character
properties. In the long run, we probably want to have functions for
checking and modifying character properties other than case. Don't know
if including ucdata is overdoing it though.
As I understand it it works by generating binary files with the
character properties. A C program for doing this exists in the sources.
These binary files can then be loaded at runtime as needed. However, if
ELinks was to use ucdata the binary data should probably be included in
the final binary.
- http://crl.nmsu.edu/~mleisher/ucdata.html
--
Jonas Fonseca
_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev
