You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm having some encoding problems with RDiscount 1.6.8. I'm not convinced that they're RDiscount's fault, but I'm not quite sure how to narrow it down any further.
Some strings in our database are producing invalid encodings when passed through RDiscount. Certain character sets seem to cause trouble - for example, the tamil character ழ - U+0BB4.
So in the original string, that codepoint is represented with the bytes 0xE0,0xAE,0xB4, but after rdiscounting we end up with just 0xE0,0xAE.
This is on a Solaris box running ruby 1.9.2p180. An OS X box running the same ruby & rdiscount version works fine. What else can I look at to pinpoint the problem some more?
The text was updated successfully, but these errors were encountered:
Hi,
I'm having some encoding problems with RDiscount 1.6.8. I'm not convinced that they're RDiscount's fault, but I'm not quite sure how to narrow it down any further.
Some strings in our database are producing invalid encodings when passed through RDiscount. Certain character sets seem to cause trouble - for example, the tamil character ழ - U+0BB4.
So in the original string, that codepoint is represented with the bytes 0xE0,0xAE,0xB4, but after rdiscounting we end up with just 0xE0,0xAE.
This is on a Solaris box running ruby 1.9.2p180. An OS X box running the same ruby & rdiscount version works fine. What else can I look at to pinpoint the problem some more?
The text was updated successfully, but these errors were encountered: