headers
Darren Cook | 1 Feb 04:31

UTF8 BOM

I'm editing UTF-8 files on linux and got bitten by the unexpected BOM
character being inserted at the front of the file. As others [1][2] have
said, "UTF-8 with BOM" and "UTF-8 without BOM" would be less confusing.
(As SciTE doesn't actually write the cookie there seems no need to
mention it.)

Now I've stripped the BOM character out, when I reopen the file it opens
as 8-bit, not UTF-8 (though it seems to be understanding it as UTF-8,
and doesn't corrupt if I then re-save). So it seems 8-bit means UTF-8 as
well, at least with my settings [3]. I think this is what someone meant
in the Dec 2006 thread when they suggested "8-bit" should be called
"default"?

Darren

[1]:
http://www.lyra.org/pipermail/scite-interest/2006-December/008325.html

[2]:
http://www.mail-archive.com/scite-interest <at> lyra.org/msg02649.html

[3]:

# Internationalisation
# Japanese input code page 932 and ShiftJIS character set 128
#code.page=932
#character.set=128
# Unicode
code.page=65001
#code.page=0
(Continue reading)

Permalink | Reply | 15 comments |
headers
Steve Donovan | 1 Feb 09:32
Picon

Re: [ANN] SciTE 1.72 with Lua 5.1

Hi guys,

I've made extman.lua and scite_other.lua compatible with Lua 5.1;
very few changes needed (loadlib is now package.loadlib, so I check
for the existence of loadlib, etc; for i,v in table is finally been
removed)

http://mysite.mweb.co.za/residents/sdonovan/new-extman.zip 

scite_other _is_ a hack, because without linkable Lua symbols
one can only import a simple function taking no arguments;
hence the temporary files.  OpenOther _can_ open files with
spaces, but either use '/' or '\\' in Lua strings.  I agree that
a Linux version would be useful, but the DirectorExtension
interface is rather different and .. subtle. (I.e. I don't
fully understand it ;))

steve d.

--

-- 
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.

CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html 

CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frank Wunderlich | 1 Feb 16:27
Picon
Picon

Re: strange problem (LUA: favorites - backup)

i found the problem...
the lua-function Open() opens the given file exclusive, so i cannot 
rename it while it's open. opening a file in scite "normal" let me 
rename the file.
Can the lua-function changed to work like "normal" open?

regards frank
Permalink | Reply | 7 comments |
headers
Ervin Peters | 1 Feb 20:31
Picon
Favicon

user properties, file patters xml

Hi,

SciTE is my preferred Editor in my Gentoo-Linux Enviroments. I
recognized a little which might be of interest for others.

The structure of evaluating the properties file is somehow like from
general to user specific. For that reasen I coied all my modifications
to my user properties file, because it is never touched on update time.

That workd vor the most things like all the suggestions of the global
properies, the keywords.$(file.patterns.sql) but not for the

file.patterns.xml=*.tmpl;*.xml;*.xsl;*.svg;*.xul;*.xsd;*.dtd;*.xslt;*.axl;*.xrc;*.rdf

which is part of the html properties. It works if I change th html
properties file, but not if I use that line in user properties.

So how can I store my wish to have *.tmpl files displayed as xml in my
user properties?

ervin

--

-- 
Ervin Peters
Auf dem Steinberge 14
D-99425 Taubach

+49 172 2043926
Permalink | Reply | 1 comment |
headers
Don Kinzer | 1 Feb 21:31

bug in AfterName()

Recently, when attempting to add a new command line option to my personal
build of SciTE, I encountered a coding error that has been there since at
least v1.62.  In SciTEBase.cxx, the function AfterName() contains this
conditional:

while (*s && ((*s == '.') ||
  (*s >= 'a' && *s <= 'z') ||
  (*s >= 'A' && *s <= 'A')))

Clearly, the third line is coded incorectly; the second part should read *s
<= 'Z'.  The effect of this error is that option names with upper case
characters are not correctly recognized.

Don Kinzer
Permalink | Reply | 1 comment |
headers
Neil Hodgson | 2 Feb 00:06
Picon

Re: bug in AfterName()

Don Kinzer:

> Clearly, the third line is coded incorectly; the second part should read *s
> <= 'Z'.  The effect of this error is that option names with upper case
> characters are not correctly recognized.

   OK, committed.

   Neil
Permalink | Reply | 0 comments |
headers
Neil Hodgson | 2 Feb 00:28
Picon

Re: user properties, file patters xml

Ervin Peters:

> That workd vor the most things like all the suggestions of the global
> properies, the keywords.$(file.patterns.sql) but not for the
>
> file.patterns.xml=*.tmpl;*.xml;*.xsl;*.svg;*.xul;*.xsd;*.dtd;*.xslt;*.axl;*.xrc;*.rdf
>
> which is part of the html properties. It works if I change th html
> properties file, but not if I use that line in user properties.

   This is a bug that file pattern properties are evaluated at the
level of that property rather than looking at higher priority
properties. So lexer.$(file.patterns.xml) which is in global
properties looks for file.patterns.xml in global properties and not
user properties.

> So how can I store my wish to have *.tmpl files displayed as xml in my
> user properties?

   Include properties like *.$(file.patterns.xml)= in your user
properties as well:
lexer.$(file.patterns.xml)=xml

   Neil
Permalink | Reply | 0 comments |
headers
Neil Hodgson | 2 Feb 00:34
Picon

Re: strange problem (LUA: favorites - backup)

Frank Wunderlich:

> the lua-function Open() opens the given file exclusive, so i cannot
> rename it while it's open. opening a file in scite "normal" let me
> rename the file.
> Can the lua-function changed to work like "normal" open?

   Do you mean "io.open" or "scite.Open"? If you are using the lua
"io.open" function then you should close the file when you want it to
be accessible to other code.

   Neil
Permalink | Reply | 6 comments |
headers
Kein-Hong Man | 2 Feb 03:48
Picon

Re: teste the scite version inside a lua script

Neil Hodgson wrote:
> Kein-Hong Man:
> 
>> An scite.VERSION entry in the Lua extension would be helpful... is
>> such a scheme acceptable?
> 
>    If there was a reasonable way for it to be set, preferably
> automatically. There are already too many locations where I have to
> change the version number for each release.

I searched for "72" in a CVS copy, and for SciTE we have:
SciTEBase.cxx
SciTERes.rc

apart from the docs...

If we put the versions in SciTE.h, the Lua extension can get the 
version number from there and create a string constant in "scite".

Can't help with the docs, though, that will need a Python or Perl 
script...

--

-- 
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia
Permalink | Reply | 2 comments |
headers
Neil Hodgson | 2 Feb 06:10
Picon

Re: teste the scite version inside a lua script

Kein-Hong Man:

> I searched for "72" in a CVS copy, and for SciTE we have:
> SciTEBase.cxx
> SciTERes.rc
> 
> apart from the docs...
> 
> If we put the versions in SciTE.h, the Lua extension can get the version 
> number from there and create a string constant in "scite".

    Now look at the different formats of that version number in the two 
files:

PRODUCTVERSION	1, 7, 2, 0
VALUE	"FileVersion",	"1.72\0"
AddStyledText(wsci, " 1.72\n", 1);

    I don't know if the version of the preprocessor available with 
resource compilers is capable of stringizing or arithmetic but if 
someone else wants to try it...

> Can't help with the docs, though, that will need a Python or Perl script...

    When I last investigated this it looked like it needed scripting to 
handle the variety of cases. The version.txt file in the scintilla root 
directory is a remnant of that investigation.

    Neil
(Continue reading)

Permalink | Reply | 1 comment |

Gmane