Magic Magpie (quirrc) wrote in lj_clients,
Magic Magpie
quirrc
lj_clients

UTF

It looks like LJ accepts raw (non-encoded) UTF8 from clients. I do not know whether that is an error or on purpose but it was one of the reasons why some (i.e. random) users on Asian locales (CJK) could not use Semagic for a long time receiving "Invalid UTF stream error". That was definitely an error in Semagic too (of the same nature as described here, i.e. isalpha and other similar functions that are used in urlencoding are locale dependent (surprise surprise)) but it would have been discovered long time before if LJ were not accepting it non-encoded at all. It looks like for some strings it works but other are accepted only encoded. I may suggest that the code at LJ should be at least re-checked (if not to block non-encoded) because it may be associated/lead to some other errors (maybe somehow related to composite/precomposed stuff, I'm not a specialist here).
Subscribe

  • 302: lj_dev

    In the interests of consolidating all LiveJournal development-related discussion, we're going to be closing down this community. The same…

  • Plain text to LJ

    I have an old blog from xanga that's in html/plain text and I want to move it over here. Which client would be the best to do this? I also want to…

  • ljKlient 0.2.0 Preview Release 1

    Today marks another milestone in the development of ljKlient — as the first preview of the 0.2 series is released.  Please go to the project…

  • Post a new comment

    Error

    Comments allowed for members only

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

  • 0 comments