#35 Support for ANSI-character set

closed
nobody
5
2008-08-20
2002-06-04
No

Many users have wished better support for ANSI-character set in
conjunction with LaTeX language-packages.

I.e. on
older systems it was necessary to insert "a into the text to get the
german ä in the output. The users wish some kind of auto
replacement (typing ä will insert "a in the text) and support for the
structure view, to recognize such special characters and
convert them for the display.

Also desirable would be an
option to choose the character set, when saving a file and let
TXC transform it.

Discussion

  • Gunnar Wagenknecht

    Logged In: YES
    user_id=372260

    Should be higher rated because it would improve the
    usuabillity for us very much.

    I think the best solution is to have something like a
    swichtable auto-replacement on opening and saving files link
    WinEdt provides.

     
  • Tino Weinkauf

    Tino Weinkauf - 2003-01-20

    Logged In: YES
    user_id=439379

    beccari@polito.it wrote about this topic:

    Read/Write translations of national chars

    The suggestion you give of using babel and the latin1
    inputenc (possibly automatically changing, say,
    u-umlaut with "u in the input file, according to the babel
    german language definition file) is a halfway
    solution to the problem of national characters; in facts the
    prepared LaTeX file will compile correctly in the
    local computer, but will exhibit problems when ported to
    another platform. Even if codepages are getting
    more and more standardized, there remains the fact that when
    you upload a file prepared on another
    computer with another codepage chances are that chars with
    code higher than 127 might appear different
    on the screen and will not compile correctly because they do
    not comply with latin1. I had a problem of
    this kind when a student of mine came over with a test LaTeX
    source written down with another
    codepage.

    The solution is that every tex file is saved such as not to
    have any char code > 127; babel strings are
    good for german and some other languages, but miss to solve
    the problem with other language
    descriptions that do not use the " active char or use it in
    a different way. The real solution is to translate
    input national chars to standard TeX sequences while writing
    and to translate the standard TeX
    sequences while reading. This is what other text editors
    specifically suited for LaTeX do (for example
    WinEdT: shareware).

    The other point concerning national characters is the fact
    that national keyboarda contain some of the
    accented or otherwise special charaters; US keiboard contain
    non of them; nevertheless many text
    editors mimick the shortcuts provided for by MS Word, so
    that for example <Ctrl>+' followed by a valid
    vowel, say e, produces eacute, <Ctrl>+` follwed by e
    produces egrave, <Ctrl+c, followed by c produces
    ccedilla, and so on; they will be saved in the tex file as
    \'{e}, \`{e}, \c{c} respectively. In this way it is much
    more confortable to read the text on screen while editing,
    and one is sure the saved file is absolutely TeX
    correct and platform independent, since it does not contain
    any charcode >127.

    beccari@polito.it

     
  • Tino Weinkauf

    Tino Weinkauf - 2003-01-20
    • priority: 3 --> 5
     
  • Tino Weinkauf

    Tino Weinkauf - 2005-01-26

    Logged In: YES
    user_id=439379

    See also

    564240 Auto Replace

     
  • Tino Weinkauf

    Tino Weinkauf - 2008-08-20
    • status: open --> closed
     


Anonymous

Cancel  Add attachments





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

Sign up for the SourceForge newsletter:





No, thanks