On Wed, Dec 27, 2017 at 11:45 PM, Dawid Weiss <[email protected]> wrote: >> 1) Fix (or tell someone else to fix) whatever is producing invalid >> content. That code is broken. > > Strong +1 to this one and thank you for stating this. We sometimes get > the same request > from customers who have invalid UTF-8 (or XML files with valid UTF-8, > but illegal characters). I always try to redirect them to fix the > problem at the core, there is no better way. > >> 2) Use a single-byte encoding like ISO-8859-1 (latin-1) -- or one of >> other 8859-x encodings -- to decode. > > While technically a solution this sets you back 30 years to the world > with byte-based codepages. If you dodge the problem now, it's going to > bite you in the future (somebody will complain sooner or later and > it'll be even harder to diagnose where illegal characters come from). > > Fix the problem up the processing chain. If this is not possible, > report and omit invalid input files.
Nothing much to add. I agree. Adding work-arounds often ends up causing more work for everyone involved, without making anyone's life easier. -+ Tatu +- > > Dawid > > -- > You received this message because you are subscribed to the Google Groups > "jackson-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "jackson-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
