Hi. On Mon 2009-01-26 09:31, Julien Danjou <[email protected]> proclaimed: > At 1232932680 time_t, Frank Blendinger wrote: > > Does anyone know a way I could work around this? Either by enhancing the > > perl snippet somehow, or by telling awesome somehow to ignore these > > errors? > > > > The bad thing is that once I have just one such character in my text, > > the whole notification won't show up. > > Yes, pango really wants good UTF-8, or it will spit at your face just > like it does. So no, you can't "bypass" this. You need to really > re-encode your text.
OK, thanks for the clarification.
I know this is not really the topic of this list anymore, but does
anyone can give me a hint how I could fix those bad UTF-8 chars?
I thought about using recode, but since my text is already UTF-8
(besides the invalid chars), and the output has to be UTF-8, too, I
could only do ``recode UTF-8..UTF-8'', which does not help.
Greetings,
Frank
--
Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A
Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A
"Just because I don't care doesn't mean I don't understand."
(Homer Simpson)
signature.asc
Description: Digital signature
