From: Mari Voipio <mari.voipio@iki.fi>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Russian/Cyrillic - no woes, happy now!
Date: Thu, 05 Feb 2009 12:34:21 +0200 [thread overview]
Message-ID: <498AC0AD.2060200@iki.fi> (raw)
In-Reply-To: <6faad9f00902041140u6203dcaayee885c93222a2555@mail.gmail.com>
Mojca Miklavec wrote:
> On Wed, Feb 4, 2009 at 4:18 PM, Mari Voipio wrote:
>> Wolfgang Schuster wrote:
>>> 3. Select "UTF-8" in menu File/Encoding
>> This solved problem number 1: how to do UTF in SciTe.
>
> The problem is that you need to do that every time. There is some file
> with user settings that you can access through menu. Do not ask me
> where it is since I cannot try it now, but it's very handy since you
> only do it once and then UTF-8 will always work out-of-the-box.
Agreed. However, once I knew I should be looking for this, I found one
solution to this problem at
http://www.nabble.com/default-encoding-to-utf-8-cookie-td5946114.html
The thing to do is to open the SciTe global properties (Options | Open
Global Properties) and to find the spot that says
# Internationalisation
# Japanese input code page 932 and ShiftJIS character set 128
#code.page=932
#character.set=128
# Unicode
#code.page=65001
code.page=0
#character.set=204
# Required for Unicode to work on GTK+:
#LC_CTYPE=en_US.UTF-8
#output.code.page=65001
Then uncomment the line code.page=65001 and comment the line code.page=0
(for us Windows dummies: move the hash mark # down by one line).
After this change everything opened in Scite in Windows is handled as
UTF-8 (GTK+ users will take note of the second comment). Remember to
save the properties file before closing it.
Caveat: This is advisable if you use Scite only with UTF-8 encoded
files. If you use SciTe for files with other encoding, it is not a good
idea. Why, you ask?
Because in the Encoding menu under File there's no way of switching a
tab back to for example Windows Iso-Latin1 or whatever else your files are.
I know SciTe menus are adjustable so if somebody knows of a way to
adding 'switch tab to code.page 0' or 'windows default encoding' or
something similar to the Encoding menu, that'd be very much appreciated.
Until then, I probably have to give up using SciTe as my html editor or
some other people will be veerryyy annoyed...
Mari
(...who's next job is to convert a pile of files into UTF-8...)
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-05 10:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 12:51 Russian/Cyrillic woes - Windows XP Mari Voipio
2009-02-04 14:32 ` Wolfgang Schuster
2009-02-04 15:18 ` Russian/Cyrillic - no woes, happy now! Mari Voipio
2009-02-04 15:29 ` Wolfgang Schuster
2009-02-04 19:40 ` Mojca Miklavec
2009-02-05 10:34 ` Mari Voipio [this message]
2009-02-05 10:42 ` luigi scarso
2009-02-05 12:21 ` Russian/Cyrillic - UTF-8 stuff Mari Voipio
2009-02-05 12:34 ` Wolfgang Schuster
2009-02-06 14:41 ` Mojca Miklavec
2009-02-06 15:18 ` Yue Wang
2009-02-05 11:50 ` Russian/Cyrillic - no woes, happy now! Mojca Miklavec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=498AC0AD.2060200@iki.fi \
--to=mari.voipio@iki.fi \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).