problems encoding hebrew text from access 97

Ask a Question related to Coldfusion Database Access, Design and Development.

  1. #1

    Default problems encoding hebrew text from access 97

    Hello,

    I've moved a web site that I've built from a server that uses CF 5 to a server
    that uses CF MX.

    As seen in the page - [url]http://www.yes-od.com/kesher.cfm[/url]
    The static hebrew HTML text apears just fine, but the dynamic hebrew text from
    the access 97 data base apears in "jibrish".

    Can anyone have a look at tell me what can be done so that the site will look
    as it should be?

    Thankshttp://www.yes-od.com/kesher.cfm

    rami1972 Guest

  2. Similar Questions and Discussions

    1. XML text encoding
      Anyone have any experience with this? I'm loading files from an XML file that is encoded as a UTF-8 files. I tried some other encoding formats,...
    2. CGI.pm: encoding problems
      I have a problem with inputing utf-8 via a text window using CGI.pm. This problem concerns UTF8 so apologies for posting something with Chinese...
    3. Encoding Problems
      Hi, I'm using the MSXML4 XMLHTTP object to send soap messages. Yesterday all worked fine, and I think the installation og either XP SP2 or .net...
    4. encoding problems with MX
      i dont know if there is a way to do it or a patch to fix it or how many times this question has been asked here but i will ask it. how can i use...
    5. FileMaker and encoding problems
      Hi, My friend is using filemaker to store his workes. Using their working days & hours, personal info. He has an encoding problem. Can anyone...
  3. #2

    Default Re: problems encoding hebrew text from access 97

    what encoding did you use to enter the data in the first place? mx
    defaults to utf-8. you might get lucky, try simply changing the access
    driver to "access for unicode" & see what happens. you have to decide
    what encoding to use, unicode (which i laways recommend) or a hebrew
    codepage (provided that's what you used in the first place). decide that
    first.

    btw this has no effect in mx and is in fact misleading as an artifact
    (if that's why it's there): <meta http-equiv="Content-Type"
    content="text/html; charset=windows-1255"> the page is actually
    rendered using utf-8.
    paulh Guest

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139