I think the solution should be that the user has to convert the message form whatever charset she uses to the charset needed by the lcd - and definitely *NOT* support all available charsets in owfs !!!
anyhow - if the user isnt aware of different charsets - she would also not know what message_* to write to ... well, hey ... ist unicode after all ;) +1 vote for not having needless complexity inside owfs ! greets, m. Am Mittwoch, den 26.01.2011, 21:01 -0200 schrieb Roberto Spadim: > the problem is, how to identify what´s the filesystem charset, after > this everythink is easy > maybe a "function" on owfs > echo asdfadf > message > echo asdfasdf > message_latin1 > echo asdfasdf > message_cb850 ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
