-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extended characters get wrong when using twidge #51
Comments
Are you passing your update on the command line or by stdin? Whichever On 08/01/2013 11:06 AM, joje47 wrote:
|
I'm having the same exact problem. My locale config: LANG=en_US.UTF-8 |
Can you try running twidge status 736519909178548224 for me? On my system, I see: <Lufthansa_DE> "Abenteuer hält meinen Geist frisch und macht meine If that doesn't work, please install ghc and run ghci, then type: :m System.IO and tell me what it says. |
Hi,
Thanks for this excellent program. I have used quite some time to figure this out, but failed. I'm not sure if its an issue with twidge or not, but let's see:
When using twidge update with locale UTF-8(sv_SE) and extended characters, such as åäö, those does not show up in twitter. They will be replaced with a symbol containing a question mark instead.
That is of course a big problem for me. Are there any way to get around this? I did some tests with enconv uconv etc.. but I didn't get it right.
I use Firefox in Linux Mint and it is also using the locale UTF-8(SV_se) so I don't see why I should need to use another encoding..
Any ideas?
Sincerely /George
The text was updated successfully, but these errors were encountered: