#208 Shift-JIS files are not displayed correctly

open
None
5
2004-11-13
2004-11-12
DF Sean
No

Files with Japanese text which have been saved in
Shift-JIS encoding are not opened as Shift-JIS so all
of the Japanese characters are "mojibake" -- crazy
unintelligible characters (not Japanese).

This is true for every Shift-JIS document I've tried to
open in Screem. They open fine in Bluefish, Quanta,
and other text editors.

I'm using Screem 0.10.2 on Gnome 2.8. Please see the
attached file.

Discussion

  • DF Sean

    DF Sean - 2004-11-12

    PHP file containing Japanese text and encoded as Shift-JIS

     
  • David A Knight

    David A Knight - 2004-11-13

    Logged In: YES
    user_id=736

    screem currently has no way of knowing what format the
    attached file is in. bluefish fails to open it correctly
    here as well unless the default character set is set to SJUS.

    As with bluefish, setting the screem default character set
    to Shift-JIS it displays fine in newer versions than 0.10.2.
    There is a bug in the latest release (0.12.0) which will
    cause screem to crash when converting to the default
    character set though, which is probably also present in
    0.11.x releases.

    In the longer term screem should hopefully support auto
    detection of the character set.

     
  • David A Knight

    David A Knight - 2004-11-13
    • assigned_to: nobody --> davek
     
  • DF Sean

    DF Sean - 2004-11-13

    Logged In: YES
    user_id=1108264

    Okay, so if 0.10.2 and 0.12.0 don't work and 0.11.x probably
    won't work, please tell me which version probably *will* work.

    >>In the longer term screem should hopefully support auto
    >>detection of the character set.
    In the interim, perhaps it would be easier to just allow the
    document encoding to be manually selectable from a menu?

    If I could do that, I'd use Screem everyday. But as it is,
    I can't use it because I'm always doing bilingual sites in
    western and shift-jis. Any hope for me?

     
  • David A Knight

    David A Knight - 2004-11-13

    Logged In: YES
    user_id=736

    only a CVS version will work at the moment. A new version
    will probably be released in the next few days if you
    cant/dont want to use the CVS version.

    The best recommendation is to use UTF-8 whenever possible as
    you then wouldn't need to use different character sets for
    different languages.

     
  • DF Sean

    DF Sean - 2004-11-13

    Logged In: YES
    user_id=1108264

    Okay, I guess I'd like to try the cvs. Can you point me to
    a repository? Thanks ;-)

     
  • David A Knight

    David A Knight - 2005-11-14

    Logged In: YES
    user_id=736

    CVS now supports specifying the character in the file select
    dialog for both opening files and sites, and from the open
    location dialog for both.

    When opening a site with a specific character set all files
    in that site will be treated as that character set.

    When inserting from a file the file selector will also allow
    you to specify the encoding of the file being inserted.

    The character set in use will be displayed on the tooltip of
    the tab for the document.

    opening from recent files / recent sites will does not allow
    specifying the character set as there is no way to store
    this, likewise drag / dropping files will not allow the
    charset to be specified.

    Attempting to mix character sets in a site will probably
    result in things going wrong. There is no "convert to"
    option available for sites. auto detect will act just like
    before so won't pick up Shift-JIS.

    save as will allow a specific charset to override what the
    file already thinks it is (based off specifying when
    opening, a meta tag, or global screem default otherwise) as
    will save copy / save as template.

    I'm not marking the bug fixed though as you mention
    multilingual sites, so presumably screem will need to be
    able to deal with different charsets within the same site.

     

Log in to post a comment.