As3 mp3 encode problem

Hi,
We are developing an app that could play mp3s from a music store. We found that the downloaded mp3 from the store can't play be as3's Sound class. The file's information can be load, but just not to play. Same code (something like new Sound(); load(urlrequest);play();..) will work to some of other mp3s. I've searched from internet. Looks like this is only way to play mp3s by AS3. Some older AS2 code could play these mp3s by sound.loadSound(). I don't understand why the old method is better than the newer one, and it is in same flash editor and player. I re-encoded the mp3s by Adobe Media Encoder, and the AS3 player will work. But I can't do it for every customer's downloaded mp3. From internet, I can't find what is the specification of Flash friendly mp3 Encode. And every other mp3 player can play these mp3s even Flash AS2.
Please help!
Andy

The reason I listed as3 and as2 code with local mp3 is showing you even the code is simple like that, it is still not working. So I don't expect it could work with more complicated situation, and how wired it isthat AS2 code could work but not AS3.
It will be an iOS app, but anyway it will be running by swf, right?
The music will be downloaded from the music store, but it will be running in the local folder, not stream from internet.
So the code for music playing will just be like that:
import flash.media.*;
  var snd:Sound = new Sound();
  snd.load(new URLRequest("Music.mp3"));
  snd.play();

Similar Messages

  • ITuned mp3 Encoder Problem

    Whenever I encode songs, I do so in mp3 format (very universal). I encode at 256 kpbs. However, one time I accidently did a 192 kbps encoding, but it sounded like a 112 kbps endcoding. Then I did a 112 kbps, and I was right. Then I brough up Nero so I could view the frequency range. it was worse than the 112 kbps... what is up with that. it cut off at about 12 khz on 192.... it cut off at about 12.5 or 13 khz with 112. Then I did a 256 encoding of the same song, and it cut off at about 15khz, which was about 128 kbps normally. Then I looked at previously encoded songs using this same iTunes that I just did (6.0.2.23), and at 256 they were fine, were normal. I did that one about 2 days ago. Then I viewed songs i imported yesterday. It had those bad effect tat it does now, cutting off at 16 khz and sounding like a 128 - 160 kbps. This has NEVER happened to me before on any otehr iTunes. I was wondering if this was a glitch or is fixed in the new 6.0.3 one that was released about 3 days ago. Thanks. I appreciate any feedback.
    ROB C

    I solved the problem.
    ITunes preferences are stored in a hidden directory here:
    C:\Documents and Settings\Username\Programdata\Apple Computer\ITunes\iTunes.pref
    (Programdata might be called something else in the English version of XP, I have the Norwegian version...)
    Close ITunes.
    Open this file in a text editor that can handle binary files, for example Textpad (www.textpad.com).
    Remove the two lines starting with keys
    iTunes.exe:MP3 Encoder:Custom
    iTunes.exe:MP3 Encoder
    Start ITunes. Set your desired import bitrate.
    It should now be saved - and be picked up again next time you open your preferences.
    Actually it was saved all the time, but something corrupts this file disabling ITunes from picking up the correct mp3 encoder settings. I guess the 160kb/s setting is the default showing up when no settings are present.
    Hope this works for others having this problem as well!
    Regards,
    Vidar

  • Mp3 Encoding Problem plz help me .

    I have Muvo N200 and while to use MP3 Encoding feature mp3 player show an Error : "Unrecovered Error" & shut down imediatly . what's this & what's solution of this problem plz

    Did the MP3 encoding software shut down (if so, what software?), or the player itself show the error?

  • Restoring MediaSource 3.30.21 MP3 encoding functionality in MediaSource 5, in Vi

    I own the Zen Sleek Touch Photo. I have been for the last year or two been using MediaSource 3.30.2
    I read from Creative that I could retain MP3 encoding functionality in MediaSource 5 as long as I
    kept MediaSource 3.30.2 installed. This is fine all except for the problem that I can't successfully
    install MediaSource 3.30.2 in Vista automatically. However, I am fully capable of manually installing
    whichever piece of MediaSource 3.30.2 that flags MediaSource 5.
    There are only a few directorys and places in the registry that MediaSource 3.30.2 installs to.
    I'd like to know which file or registry string, or combination MediaSource 5 looks for, for the
    encoding functionality.

    gblackwo wrote:
    Well, I gave up trying to get mediasource5 to work, and let me encode mp3s. So I found it easier to hack mediasource 3 to install into vista 64bit. It works.
    To enable MP3 encoding in MediaSource v5 you need to buy the Creative MP3 Audio Pack. http://buy.soundblaster.com/_creativ...FX685ASKJBLYY2 The pack includes the MP3 plug-in (composed of 2 files), so you are wasting your time trying to enable it in the Registry.

  • MP3 encoder VBR Options doesn't work anymore

    Hi everyone !
    I always used iTunes mp3 encoder to rip my CD's with the VBR option ON and it worked fine until now.
    Indeed since 10.3 the VBR option doesn't seem to be working no more : the output is a CBR mp3 file either I tick or not the VBR option box !
    Does anyone have the same problem ? Is there a way to solve this issue ?
    Thank you

    We can't know. You have not provided any system info or other useful technical details.
    Mylenium

  • MP3 Encoder Import  Bitrate is not saved by ITunes

    Hi!
    The importing bit rate for the MP3 Encoder is not saved by ITunes.
    This is obviously a bug only present in combination with special software / hardware, since several people have already have posted this problem on this forum.
    I am running
    - ITunes 6.0.1.3
    - Windows XP Home Edition SP2
    on a
    HP Pavilion zd8000.
    What I need to know is where these settings are stored, so that I can edit them directly to resolve the problem.
    If this is not possible, how can I debug to find out what is going on?
    I have reinstalled several times, and the system is not behaving consistently. I have played with different versions of ITunes. I have removed all ITunes entries in the registry between installations. I have succeeded in solving the problem, but it has reoccured.
    Please advice.
    Thanks in advance!
    Regards,
    Vidar
    email: [email protected]

    I solved the problem.
    ITunes preferences are stored in a hidden directory here:
    C:\Documents and Settings\Username\Programdata\Apple Computer\ITunes\iTunes.pref
    (Programdata might be called something else in the English version of XP, I have the Norwegian version...)
    Close ITunes.
    Open this file in a text editor that can handle binary files, for example Textpad (www.textpad.com).
    Remove the two lines starting with keys
    iTunes.exe:MP3 Encoder:Custom
    iTunes.exe:MP3 Encoder
    Start ITunes. Set your desired import bitrate.
    It should now be saved - and be picked up again next time you open your preferences.
    Actually it was saved all the time, but something corrupts this file disabling ITunes from picking up the correct mp3 encoder settings. I guess the 160kb/s setting is the default showing up when no settings are present.
    Hope this works for others having this problem as well!
    Regards,
    Vidar

  • Wave Stuido 6.0 - MP3 encoder

    I have Creative Wave Studio 6.20.4 with MP3 encoder and Wave Studio 7. without MP3 encoder.
    I don't recall if WS 6.20.4 came with the MP3 encoder or if I upgraded it to include the MP3 encoder. I don't seem to find anything on my system about upgrading WS 6.20.4 to include MP3, so what I'm asking is if WS version 6.xx came with a MP3 encoder or it that was an extra cost item, before I go nuts trying to find upgrade info (like a key) that doesn't exist because it was part of the standard Wave Studio 6.xx and not a upgrade.

    I solved the problem.
    ITunes preferences are stored in a hidden directory here:
    C:\Documents and Settings\Username\Programdata\Apple Computer\ITunes\iTunes.pref
    (Programdata might be called something else in the English version of XP, I have the Norwegian version...)
    Close ITunes.
    Open this file in a text editor that can handle binary files, for example Textpad (www.textpad.com).
    Remove the two lines starting with keys
    iTunes.exe:MP3 Encoder:Custom
    iTunes.exe:MP3 Encoder
    Start ITunes. Set your desired import bitrate.
    It should now be saved - and be picked up again next time you open your preferences.
    Actually it was saved all the time, but something corrupts this file disabling ITunes from picking up the correct mp3 encoder settings. I guess the 160kb/s setting is the default showing up when no settings are present.
    Hope this works for others having this problem as well!
    Regards,
    Vidar

  • I am trying to create mp3 version of itune songs.  I have gone through the preference sequence to be mp3 encoder but this is not having any effect.  I have also tired from file tab to create a version but this is not available to action

    I am trying to create mp3 version of itune songs.  I have gone through the preference sequence to be mp3 encoder but this is not having any effect.  I have also tired from file tab to create a version but this is not available to action showing as lite grey.
    Any help would be appreciated

    I am trying to create mp3 version of itune songs.  I have gone through the preference sequence to be mp3 encoder but this is not having any effect.  I have also tired from file tab to create a version but this is not available to action showing as lite grey.
    Any help would be appreciated

  • Encoding problems in email while on Windows Mail app

    Hello.
    I have a question concerning email and encoding problems in the Windows Mail App in Windows 8.1.  I have encountered a problem with an email I received, while reading, I see strange ASCII characters in one email.  I have never encountered it in
    my web browsers nor Gmail, just the Mail App.
    I was referred to come here when I had asked a similar question there:
    http://answers.microsoft.com/en-us/windows/forum/windows8_1-ecoms/strange-foreign-ascii-characters-appearing-in/911f8a44-c302-4fa1-bcaa-3297b32d9120
    I don't know which forum to go to so I picked here.
    Is there any way that it can be resolved.  I tried to troubleshoot, nothing worked; I even synched, to no avail.
    I look forward to a response.
    JB

    Hi JB,
    The responder on answers was a bit confused. The MSDN forums are for developers to discuss writing their own apps. We cannot help with problems using Windows or its built-in apps.
    If the folks on answers cannot help then you may need to open a support incident. See
    http://support.microsoft.com , or the folks on answers may be able to direct you to the specific page for the Windows Mail app.
    --Rob

  • Encoding problem while reading binary data from MQ-series

    Dear all,
    we are running on 7.0 and we have an encoding problem while reading binary data from MQ-series. Because we are getting flat strings from queue we use module "Plain2ML" (MessageTransformBean) for wrapping xml-elements around the incoming data.
    The MQ-Series-Server is using CCSID 850, which we configured in connection parameters in communication channel (both parameters for Queuemanager CCSID and also CCSID of target).If there are special characters in the message (which HEX-values differ from codepage to codepage) we get errors in our adapter while executing, please see stack-trace for further analysis below.
    It seems to us that
    1. method ByteToCharUTF8.convert() expects UTF-8 in binary data
    2. Both CCSID parameters are not used anyway in JMS-adapter
    How can we solve this problem without changing anything on MQ-site?
    Here is the stack-trace:
    Catching com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
        at com.sap.aii.af.modules.trans.MessageTransformBean.throwModuleException(MessageTransformBean.java:453)
        at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:387)
        at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
        at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
        at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
        at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:84)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter(ConvertBinaryToXiMessageFilter.java:304)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:112)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:87)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:123)
        at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:59)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.InboundCorrelationFilter.filter(InboundCorrelationFilter.java:60)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.JarmMonitorFilter.filter(JarmMonitorFilter.java:57)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62)
        at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
        at com.sap.aii.adapter.jms.core.channel.SenderChannelImpl.doReceive(SenderChannelImpl.java:263)
        at com.sap.aii.adapter.jms.core.channel.ChannelImpl.receive(ChannelImpl.java:437)
        at com.sap.aii.adapter.jms.core.connector.MessageListenerImpl.onMessage(MessageListenerImpl.java:36)
        at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
        at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
        at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4249)
        at com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run(SessionAsyncHelper.java:537)
        at java.lang.Thread.run(Thread.java:770)
    Caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
        at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:714)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:538)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:528)
        at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:471)
        at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:364)
        ... 36 more
    Caused by: sun.io.MalformedInputException
        at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:270)
        at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
        at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
        at java.io.InputStreamReader.read(InputStreamReader.java:208)
        at java.io.BufferedReader.fill(BufferedReader.java:153)
        at java.io.BufferedReader.readLine(BufferedReader.java:316)
        at java.io.LineNumberReader.readLine(LineNumberReader.java:176)
        at com.sap.aii.messaging.adapter.Conversion.convertPlain2XML(Conversion.java:310)
        at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:709)
        ... 40 more
    Any ideas?
    Kind regards, Stefan

    Hi Stefan,
    for the first MTB now we are using only one parameter: Transform.ContentType = text/plain;charset="ISO-8859-1"
    The second MTB, which does the XML-Wrapping, is configured like this:
    Transform.Class = com.sap.aii.messaging.adapter.Conversion
    Transform.ContentType = application/xml
    xml.conversionType = SimplePlain2XML
    xml.fieldNames = value
    xml.fieldSeparator = §%zulu§%
    xml.processFieldNames = fromConfiguration
    xml.structureTitle = payload
    Both CCSID configuration parameters from the "Source"-Tab we've set to 850.
    Now, we don't get an error anymore - sun.io.malformedInputException - , but, unfortunately, now special character conversion succeeded (we need an "ß" and we get an ISO-HEX-E1 -> á).  E1 is (different from ISO) an "ß" in 850.
    Any ideas?

  • Encoding problem in call-back to hook URL (post parameters)

    Hello all,
    I'm encountering a character encoding problem while retrieving the content of the shopping basket from one of our provider.
    After the POST request is made by the provider to our system using the hook url, when debbuging I can see that some special characters are represented with the sign '#' (after the call the ITS_IMPORT_CONTEXT).
    In our case using the parameter http_content_charset with various values, including UTF-8, did not change the result.
    Inspecting the HTTP traffic has highlighted the following: the encoding received from the provider is related to UTF-8, but while we are expecting the hexadecimal values, we are receiving the "Unicode code points", which are not recognized by our SAP system. For more details look at the UTF-8 encoding table found here and compare the values under column "Unicode code point" with the one under column "UTF-8 (hex.)".
    As an example, for the character 'é', we are receiving the value "%E9" (the code point) instead of receiving the the hexa value : "%C3%A9".
    Do you have any idee if this can be corrected on our side or if the provider must addapt the way it's sending the POST parameters?
    Many thanks in advance for you help.
    Best regards,
    Jerome.

    Hi Jason,
    Indeed I had contacted the provider and informed them about the encoding problem and the fact that passing the parameter http_content_charset had no effect on the sent back encoding.
    They have taken into account my request and have changed the encoding used during the request to the HOOK_URL.
    Thanks to all of your for your help.
    Regards,
    Jerome.

  • Character encoding problem using XSLT and Tomcat on Linux

    Hi,
    I have an application running on a Tomcat 4.1.18 application server that applies XSLT transformations to DOM objects using standard calls to javax.xml.transform API. The JDK is J2SE 1.4.1_01.
    It is all OK while running on a development enviroment (which is Windows NT 4.0 work station), but when I put it in the production enviroment (which is a red hat linux 8.0), it comes up with some kind of encoding problem: the extended characters (in spanish) are not shown as they should.
    The XSL stylesheets are using the ISO-8859-1 encoding, but I have also tried with UTF-8.
    These stylesheets are dynamicly generated from a JSP:
    // opens a connection to a JSP that generates the XSL
    URLConnection urlConn = (new URL( xxxxxx )).openConnection();
    Reader readerJsp = new BufferedReader(new InputStreamReader( urlConn.getInputStream() ));
    // Gets the object that represents the XSL
    Templates translet = tFactory.newTemplates( new StreamSource( readerJsp ));
    Transformer transformer = translet.newTransformer();
    // applies transformations
    // the output is sent to the HttpServletResponse's outputStream object
    transformer.transform(myDOMObject, new StreamResult(response.getOutputStream()) );Any help would be appreciated.

    Probably you need to set your LANG OS especific environment variable to spanish.
    Try adding this line:
    export LANG=es_ES
    to your tomcat/bin/catalina.sh, and restart tomcat.
    It should look like this:
    # OS specific support.  $var _must_ be set to either true or false.
    cygwin=false
    case "`uname`" in
    CYGWIN*) cygwin=true;;
    esac
    export LANG=es_ES
    # resolve links - $0 may be a softlink
    PRG="$0"
    .(BTW, keep using ISO-8859-1 encoding for your XSL)
    HTH
    Un Saludo!

  • C# GWTypeLibrary - AddressBook Entry encoding problem

    Hello.
    I am using C#(Visual Studio 2005) and GroupWareTypeLibrary to develop for
    GroupWise Client 7.0.
    Working with AddressBook I have faced some problems.
    I am getting display name (AddressBookEntry.DisplayName) for all entries
    of AddressBook. Almost all DisplayNames are correct but there are some
    problems with two or three of them (there are some illegal char displayed
    instead of some char of real user DisplayName). I think it is local
    encoding problem bekause I see the same problem with the same users in
    GroupWise Client AddressBook.
    I thought display name is building not correctly but when I tried to get
    these users first and last name I have got the same problem with encoding
    in them.
    Please advice how to decide this problem.
    Regards,
    Alex.

    Sounds like a GW Client problem and not an API problem if you see it in the client address book. Technical Support should be able to help you.
    Glade,
    Novell Developer Support

  • Encoding Problems with WRT300N V2

    Hello guys,
    i have following problem:
    I have a WRT300n Router and it seems to have problems with WPA2 encoding. I have 2 different deviceses (a SMC Ethernet Bridge and a PS3) trying to connect to my Linksys wireless router. No chance in WPA2 mode but when I try in WEP-Mode, both devicec can connect to it.
    Are there known encoding problems?
    Any idea what i can do?

    It is able to use. But my router always drops the connection. WEP is no problem, but ... what about low security and Wirless N is not enabled ??

  • Encoding problem (via ORB)

    Hello,
    I posted this problem few months ago, but still havent been able to solve this.
    I have a Client Server program which communicates via ORB, i.e. using CORBA, with server running on Solaris OS and Client running on windows.
    The server returns string containing chinese characters to the client.
    However, my chinese characters dont appear properly on the client side.
    If i run the client on the Solaris OS there is no problem with it.
    I tried converting the encode of the string by getting its byte and creating
    a new string with encoding parameter. None of this seems to work.
    I can see the chinese character when the server is writing to OutputStream of CORBA, but on the InputStream of CORBA it does not
    show properly.
    Any ideas on how i can overcome this encoding problem where the C/S is
    communicating via CORBA (ORB)?
    Thanks in advance.

    Thanks for your reply
    Yes, i know the BIG5 is for Traditional Chinese and japansese is using like Shift-JIS or EUC.
    So when i try to post japanese in a BIg5 web page, i think it's normal that i can't see it in BIG5 encoding.
    But then i change the Safari default decoding to BIG5 HKSCS, the japanese appers! At the same time i can see the traditional chinese too!
    And if i use Firefox, i can both see the japanese and chinese at the default BIG5 encoding.
    So i simple think maybe safari translate my japanese into BIG5 HKSCS,not Shift-JIS. But if i use Firefox, i can get the same result with only BIG5 encoding, not BIG5 HKSCS. So i am just wondering why it's different between Safari and Firefox with the same BIG5 encoding.
    Following is a example URL
    It's a MAC discussing froum with BIG5 encoding in Taiwan.
    http://ubb.frostyplace.com.tw/viewtopic.php?t=19162
    It's a froum topic posted by me. I input some japanese into this topic
    If you browse this page with Safari BIG5 encoding, you can see a lot of question mark instead of the original japanese word that i and other people posted.
    But if you change the encoding to BIG5 HKSCS, the japanese appears. And if you using Firefox with BIG5 encoding, the japanese appears too.
    So is it someing wrong with Safari's BIG5 encoding or some other reason makes this happen?

Maybe you are looking for