Encoding - inputenc Parameter

Alessandro
2014-03-07
2014-03-28
  • Alessandro

    Alessandro - 2014-03-07

    In the “Select File Encoding” dialog there’re two columns: “File Encoding” and “inputenc Parameter”. The latter is partially empty. Can I somehow add the parameters by myself?

     
  • Tim Hoffmann

    Tim Hoffmann - 2014-03-07

    You cannot add this yourself. We made the relation some time ago based on a list found somewhere on the internet. I think there is not an inputenc parameter for every possible file encoding. But it may well be that some are missing. If so, you may post them here and well add them for the next release.

     
    • Alessandro

      Alessandro - 2014-03-15

      Tim,
      Thank you for explanation. I didn’t know how this thing works—my idea was there must be some predefined list of inputenc’s arguments.

      Could you please add two more encoding: windows-1251/CP1251 defined by “cp1251” and IBM866/CP866/csIBM866 defined by “cp866”.

      Thanks in advance!

       
  • Tim Hoffmann

    Tim Hoffmann - 2014-03-15

    Done (hg 4299 (09ef30d7f566))

     
    • Alessandro

      Alessandro - 2014-03-17

      Thanks a lot! It works well.

      However I’ve found out it’s easy to confuse TXS. The following code makes it believe the encoding is windows-1251:

      % \usepackage[cp1251]{inputenc}
      \usepackage[cp866]{inputenc}
      
       
  • Tim Hoffmann

    Tim Hoffmann - 2014-03-22

    fixed (hg 4329 (288ecd06a7cf))

     
    • Alessandro

      Alessandro - 2014-03-26

      Tim,

      The behavior is still the same in TeXstudio 2.7.1 (hg 4341+:50f3c5bdec8b+).

      The following code is opened in windows-1251:

      \documentclass{article}
      % \usepackage[cp1251]{inputenc}
      \usepackage[cp866]{inputenc}
      \usepackage[russian]{babel}
      \begin{document}
      Текст на русском языке
      \end{document}
      

      While this one is considered IBM866-encoded:

      \documentclass{article}
      % \usepackage[cp866]{inputenc}
      \usepackage[cp1251]{inputenc}
      \usepackage[russian]{babel}
      \begin{document}
      Текст на русском языке
      \end{document}
      
       
  • Tim Hoffmann

    Tim Hoffmann - 2014-03-26

    Yes. This is because the fix was directly applied to the release branch and is not yet included in the development branch, based on which 2.7.1 was built. (Note: the odd numbers in the last digit denote development versions that do not necessarily contain all features of the next release yet. Likewise they may contain features that are not yet fully tested or implemented and will not be present in the next stable release.)

     
    Last edit: Tim Hoffmann 2014-03-26
    • Alessandro

      Alessandro - 2014-03-28

      Understood. Thanks for explanation!

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks