Menu ▾ ▴

#25 UTF-8 request

2.0
closed-fixed
5
2013-07-14
2006-01-06
lolow0
No

Sorry, I think it is more a request than a bug but is
it possible to write the files in UTF8 encoding? Since,
I didn't find the feature in the file dialog and in the
preferences one, I think not.
I have all my tex files in utf8 :-), sorry.
Thanks for this good application.

Laurent

Related

Bugs: #25

Discussion

  • Syd (Sylvain) Reynal

    Logged In: YES
    user_id=412933

    Hi laurent,
    Provided you export LANG to the appropriate value before
    running jpicedt, e.g., export LANG=en_US.UTF-8 (may be
    directly inserted in /usr/bin/jpicedt script), then java
    will handle all file I/O with the UTF-8 encoding.

    Another way around (which might prove useful to Windows XP
    users) is to add "-Dfile.encoding=UTF8" to the java
    commandline inside the jpicedt script, e.g.:
    "java -Dfile.encoding=UTF8 -Xmx${JAVA_HEAP_SIZE}m etc."

    I might think, however, of adding an option for choosing the
    encoding system in the future. This belongs in the wish list :)

    Regards,
    Syd
    jpicedt dev team

     
  • Vincent Belaïche

    • labels: Parsers --> Formatters: PsTricks, eepic, ..., Parsers
    • assigned_to: Vincent Belaïche
    • Group: --> 2.0
     
  • Vincent Belaïche

    Version 2.0 of installer will have the possibility to create several shortcuts. Then for each shortcut you have an "Advanced" button which allows to select the default file encoding.

    For version > version 2.0 I may do it on a preference basis, but I think that this is not that useful in the sense that one usually stick to the same encoding.

    Anyway, I think that a prerequisite to changing the charset dynamically is to have configurable preference on a document per document basis, and this is not yet supported by jPicEdt/

     
  • Vincent Belaïche

    See also feature request #19.

     

    Last edit: Vincent Belaïche 2013-07-15
  • Vincent Belaïche

    • status: open --> closed-fixed
     
  • Syd (Sylvain) Reynal

    alors CA c'est un truc qui serait cool oui !

    On 14 July 2013 23:30, "Vincent Belaïche" vincentb1@users.sf.net wrote:

    • status: open --> closed-fixed

    Status: closed-fixed

    Labels: Formatters: PsTricks eepic ... Parsers
    Created: Fri Jan 06, 2006 04:22 PM UTC by lolow0
    Last Updated: Sun Jul 14, 2013 09:29 PM UTC
    Owner: Vincent Belaïche

    Sorry, I think it is more a request than a bug but is
    it possible to write the files in UTF8 encoding? Since,
    I didn't find the feature in the file dialog and in the
    preferences one, I think not.
    I have all my tex files in utf8 :-), sorry.
    Thanks for this good application.

    Laurent

    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/jpicedt/bugs/25/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Bugs: #25

    • Vincent Belaïche

      alors CA c'est un truc qui serait cool oui !

      Le « ÇA » c'est la demande de fonction #19 (DdF° #19) ? — c'est à dire pouvoir régler le codage document par document.

      La correction de ce bogue c'est que l'installeur permet de configurer le charset qu'on veut (argument de la ligne de commande lançant jPicEdt).

      En ce qui concerne la demande de fonction #19, je me pose la question de savoir si c'est vraiment pertinent. Selon moi l'avenir c'est qu'on fait tout en UTF-8 et qu'on utilise XeLaTeX.

      De plus je ne veut pas implanter la DdF° #19 dans la version 2.0, en effet, je ne rajoute plus de nouvelle fonction majeure — j'essaie de corriger tous les bogues en attente. Et la configuration de propriété document par document c'est l'un des quelques trucs majeurs que je voudrais avoir dans la version 3.0. Une fois que l'infrastructure sera en place pour ça, alors avoir le charset doc par doc ne sera pas trop difficile. Donc version 3.0 au plus tôt pour la DdF° #19…

       

Log in to post a comment.