#515 Follow up on #514


Regarding #514: http://sourceforge.net/p/texstudio/feature-requests/514/#7d3f

"Is it possible to implement a feature such that for example the char ö in the editor is interpreted in the latex compiler as \"{o} ?
Likewise for example that ø in the editor is interpreted as {\o} etc. ?"

I was thinking of a feature like in WinEdt where for .tex files for example ø in the editor is saved as {\o}, and when reading a .tex file {\o} is converted to ø.


  • Jan  Sundermeyer

    Jan Sundermeyer - 2013-08-06

    a feature like winEdt will not be implemented.
    Why do you think that you need that anyway, as you can work with Laten1/uftx input encoding ?

  • Tim Hoffmann

    Tim Hoffmann - 2015-06-29
    • status: open --> wont-fix
    • Group: -->
  • Mike

    Mike - 2016-07-27

    @Jan Sundermeyer.
    At first I was taken aback by your somewhat smug remark as I interpreted it.

    I have now wasted some 2 hours trying to make heads or tails of the proper formatting solution in this matter and I wish to give you the simple and justified response as to why this actually should be implemented for ease of use.

    I am Swedish by birth, and I know many other European users have this very same issue when editing massive amount of course work in their native languages for all kinds of reasons. Be it students handing in course work, theses, assignments and reports or even authors whom have recently discovered the strength in text formatting and editing for publishing purposes.

    In Swedish alone we have the following 53 892 very good reasons to actually include the use of å, ä and ö as standard entries in the simplest of text files. This has proven no difficulty what so ever for any other form of editior I have ever used before and it seems but a "hubris" to avoid inclusion of this in standard UTF8 charsets within the TeXstudio GUI and file routines.

    Number of dictionary entries in SAOL

    letter >> dictionary occurences
    %å% >> 12 262
    %ä% >> 24 608
    %ö% >> 17 022

    I am willing to bet the German language is equally laden by such umlauts though I dare not venture a guess as to how many such words exist today.

    As you stated, there are other charsets which could be used as well.
    Your respons above however lends little to actually figure out how to implement a seemingly non-existing charset as you referred to ssomething which is a) grossly missspelled and b) never have existed.

    I would guess you refer to Latin1 in stating Laten1.
    I would further guess you refer to UTF8 by your statement uftx

    Is this assumption correct, and if so, where do I find them in the GUI to enable the proper formatting of my text matter?

    Latin 1 is named ISO-8859-1 in the dropdown menu in the lower GUI menu at the bottom of the page. UTF-8 is a whole other entry and none of which can be combined.

    If they can be combined in the source of the tex-file somehow I would be very much helped by an actual string displaying the proper code to include as no such information is to be found in the included help or manual pages. At least not without first learning a heck of a lot more about the syntax and lingo used here and on the manual pages online.

    If this comment seems a bit upset, off in tone or voice, then I appologize, but as a first rule, you get what you serve.


    Finally I found the following helpful comments on an other forum.

    Immediately following the \documentclass[##pt]{article} tag, insert the following line


    This resolves the problem with the editor not using, nor compiling umlauts properly!

    Last edit: Mike 2016-07-27

Log in to post a comment.

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

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks