Alan Stern schrieb: > Any suggestions for the best way to organize all this?
First a list of all files handling Unicode and a list of all files in need of handling Unicode is needed (for all Linux). A first step would be to centralize the various implementations. Then unification into a single API of functions. From there on bugfix and expansion to handle all levels of Unicode can be added. UTF-8 C strings as main access is a logical choice. It also allows to have the sources structured to drop various functionalities. The API should provide full handling of Unicode, but should be recompilable to allow to drop surrogate handling or even drop Unicode handling completely, i. e. fall back on handling only single byte charsets. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
