Test for invalid unicode in file name

[Taavi Burns]

On 5/10/05, Madison Kelly <linux-5ZoueyuiTZhBDgjK7y7TUQ at public.gmane.org> wrote:
> Shoot, it may actually be ShiftJIS... If that is the case, how can I
> "translate" it into something that postgresql would not choke on? I,
> wrongly I guess, thought Unicode included Japanese (et. al.). How is a
> poor programmer to make a program that can handle all these different
> encodings in a sane way?

Perhaps you could use some form of LOB (CLOB/BLOB) column for this? 
Then there are no concerns about character set encoding on the
database side.  This might be an issue, though, if one attempts to
restore to filesystems which have different encodings than the source
filesystems.  In that case you'd want to detect the character set
encoding for each filesystem and munge that as you go (and hope you
don't lose anything along the way!).

-- 
taa
/*eof*/
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml