Important: This page is using cookies (cookies). Using this website without turning off cookies in browser, means that you agree for using it.
Buy Now! Features Downloads

Earn with us!

If you would like to start earning money with vBET join to Affiliate Program.
Results 1 to 5 of 5

Thread: Korean translation

  1. #1
    Senior Member
    Join Date
    Dec 2009
    Posts
    276

    Default Korean translation

    This thread doesn't look like it translated too well:
    í • œê ¸ € íƒ € ì 'í •'

    Is that because of the site encoding? Is there anything I can do short of disabling that language?

  2. #2
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    3,037

    Default

    No - it is not translated at all since it has garbage content. Most probably there went something wrong with encoding and original message came broken (what you can see). Do you know by which browser and how exactly was send this message? Can you write some test messages in Korean from different browsers on your forum? (you can take some Korean phrase i.e. from Wikipedia - I think). Maybe you can PM to author and ask him which browser was used?

    Please note that in vBET cares about forums in not utf-8 and adds appropriate information for browsers about real encoding. Unfortunately not all browsers are working correctly according to HTML standard. In vBET 4.x we solved this issue by carrying it on server side. We will do it also in next release of vBET 3.x

    PS.
    At this moment you can only remove this thread - it have broken encoding in original message :/

  3. #3
    Senior Member
    Join Date
    Dec 2009
    Posts
    276

    Default

    So even though the encoding of the forum is not utf-8, vBET will still handle the Korean characters correctly?

  4. #4
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    3,037

    Default

    Yes - those are replaced to 'safe utf-8' like #&CODE; but in vBET 3.x browser must appropriately send form data (according to encoding which we set for form). We discovered that IE is ignoring it and that is why you get this garbage message. We made server side re-encoding for IE, but it appears that we miss some configuration.

    As I wrote we already have solution for this in vBET4.x - re-encode everything on server side - and it will be included in next vBET3.x version. We will simply take care about it on server side instead of trusting browsers with that.

  5. #5
    Senior Member
    Join Date
    Dec 2009
    Posts
    276

    Default

    oh I see - thanks for explaining

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •