Re: Adding ZWSP to whitespace.characters

Roger Sperberg:

> What I'm most interested in is actually seeing some indication that a
> ZWSP has been inserted.

   This is not supported.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Adding ZWSP to whitespace.characters

Neil, thanks for pinning this down.

For a complex script like Khmer, being able to display such characters
would be especially useful for material being published in print or on
the web, or merely being shared or distributed.

Theoretically, I guess a font could be constructed in, say, FontForge
that provides a visible representation for the ZWSP. Then changing
fonts would be a way to see if ZWSP's have been inserted.

That's sort of a manual version of "view whitespace" -- except that
making whitespace visible only affects a few non-printing characters.

What is the mechanism, I wonder, by which Scintilla makes [tab] and
[space] display an arrow and a middle-dot?  It must be similar to the
mechanism for causing LF or CR  or CRLF to be displayed when End of
Line is checked.

What would it take to create something similar for ZWSP (U+200B), zero-
width non-joiner (U+200C -- used with Korean hangul and Persian
script, as well as to prevent ligatures from being used in OpenType
fonts), and zero-width joiner (U+200D, used with Korean hangul and
Arabic)? And all the special spaces such as em space, figure space and
thin space in the range U+2000 - U+200A (or U+200B, to include the
ZWSP in this group)?

The zero-width characters differ from [tab] and [space] because
representing them with a visible glyph above the baseline would change
the line-width in the display. OpenOffice.org writer deals with this

Re: Adding ZWSP to whitespace.characters

Roger Sperberg:

> What is the mechanism, I wonder, by which Scintilla makes [tab] and
> [space] display an arrow and a middle-dot?  It must be similar to the
> mechanism for causing LF or CR  or CRLF to be displayed when End of
> Line is checked.

   Line ends are handled by separate code to the main character
display loop that has a separate case for tab because of its variable
width. After text is drawn, dots may be drawn over that text for each
space.

   The display pipeline in Scintilla deals with bytes rather than
characters and has no way of easily testing for ZWSP.
whitespace.characters.<filepattern> also deals with bytes rather than
characters.

   Visible spaces, tabs, and line ends do not change the layout when
they are made visible. A ZWSP is not allocated space normally so has
nowhere to draw.

> What would it take to create something similar for ZWSP (U+200B),

   A lot of work. It also adds complexity to the core of Scintilla.

>  using a light-gray bar that the regular glyphs overprint (or maybe
> they kern left and right to create an overprint effect). Below the
> baseline a small black slash appears in the gray bar; when two or more
> successive ZWSP's appear, the gray bars don't overlap each other but

Re: Adding ZWSP to whitespace.characters

On Oct 1, 6:07 pm, "Neil Hodgson" <scintilladot...@gmail.com> wrote:
> Roger Sperberg:
>
> > What is the mechanism, I wonder, by which Scintilla makes [tab] and
> > [space] display an arrow and a middle-dot?  It must be similar to the
> > mechanism for causing LF or CR  or CRLF to be displayed when End of
> > Line is checked.
>
>    Line ends are handled by separate code to the main character
> display loop that has a separate case for tab because of its variable
> width. After text is drawn, dots may be drawn over that text for each
> space.
>

Whether it be a dot below the baseline or above the ascenders or a
line of some sort, do you think it would be possible to draw in
something (anything) over the text for a ZWSP, the way the dor is
drawn over the regular space?

>    The display pipeline in Scintilla deals with bytes rather than
> characters and has no way of easily testing for ZWSP.
> whitespace.characters.<filepattern> also deals with bytes rather than
> characters.
>
This is such a flat assertion that I don't question it.

However, I don't grasp the significance of what you're saying: that
is, I don't get how regular spaces are recognized if this distinction
disqualifies the ZWSP. (Is it that only characters in the first 256

display automatic list

Re: SciTE X11 session support

Dimitar Zhekov:

> This patch adds X11 session support to SciTE.

   Don't know how much trouble adding the SM and ICE libraries would
cause. They do make the code more specific to X. GNOME has the
GnomeClient class to mediate interaction with the session manager but
SciTE has avoided GNOME dependencies as well.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: display automatic list

That's pretty straight
type ul
then press Ctrl+Return
the list with all the words starting with ul appears...

On 3 oct, 11:30, "Hugo Petit" <hugo.pe...@gmail.com> wrote:
> Hi
> I can't found how to configure scite so as to display a list of propositions
> for autocompletion. It works well when there's only one match. For exemple,
> if I define
>
> unsigned long ulPoidsMin, ulPoidsMax;
>
> I get no match until I enter ulPoidsMi or ulPoidsma, which is not that
> useful... I'd like a list with both propositions
> (even if I try to use autocomplete.*.start.characters=_ and define ul_PMin,
> ul_PMax)
>
> Is there a solution ?
> Thanks in advance

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Using keywordclass2 in Python

Hi

This may have been explained before, but i didn't find it.

To make some Python keywords have a different colour, this works:
Put the following lines in python.properties
---------
keywordclass2.python= <move some words here from keywordclass.python>
keywords2.$(file.patterns.py)=$(keywordclass2.python)
keywords2.$(file.patterns.scons)=$(keywordclass2.python)
---------
Also make sure that a line starting with
style.python.14=
exists, is not commented out, and has a useful value.

I don't know if the scons line is necessary; I simply
duplicated what was already there for 'keywords'

======================

Replacing some existing lines, this is what I actually use now:

---------
keywordclass.python=and as assert class def del elif else \
except exec finally for from global if import in is \
lambda None not or pass print try while with

keywordclass2.python=break continue return yield raise exit

keywords.$(file.patterns.py)=$(keywordclass.python)
keywords.$(file.patterns.scons)=$(keywordclass.python)

keywords2.$(file.patterns.py)=$(keywordclass2.python)
keywords2.$(file.patterns.scons)=$(keywordclass2.python)
---------

Lower down, in the styles section:

---------
# Highlighted identifiers (keywords2)
style.python.14=fore:#9F0000,bold
---------

======================

You can put whatever you like in keywordclass2.python

I put keywords that break program flow, to make them stand out.
('exit' isn't a Python keyword; no problem, it still comes up red.)

style.python.14 sets the appearance of keywords2

======================

Neil, would it be helpful to put something like the following
in python.properties for future releases?

-----
# If you put some words after "keywordclass2.python="
# and uncomment the subsequent 2 lines, those words
# will be styled according to style.python.14

#keywordclass2.python=
#keywords2.$(file.patterns.py)=$(keywordclass2.python)
#keywords2.$(file.patterns.scons)=$(keywordclass2.python)
-----

======================

I figured this out last week with help from
a couple of previous posts (forget which now, sorry)
and a squizz at some scite source code.

It took a couple of hours to figure it out,
so I hope this will save time for many others.

Regards
Jim

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: accessing rectangular selection

is there no way to access a rectangular selection with lua?

frank

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Adding ZWSP to whitespace.characters

Roger Sperberg:

> Whether it be a dot below the baseline or above the ascenders or a
> line of some sort, do you think it would be possible to draw in
> something (anything) over the text for a ZWSP, the way the dor is
> drawn over the regular space?

   Its possible but you really should take a close look at the code to
see if you can think of a reasonable mechanism.

> However, I don't grasp the significance of what you're saying: that
> is, I don't get how regular spaces are recognized if this distinction
> disqualifies the ZWSP. (Is it that only characters in the first 256
> positions can be whitespace since they can be represented in a single
> byte?)

   Most common encodings (apart from EBCDIC and escape based
encodings) are supersets of ASCII so any byte <= 127 is identical in
meaning to ASCII. Therefore byte value 0x20 is always a space. If
encoded in UTF-8 a ZWSP is the three byte sequence [e2, 80, 8b]. You
could include all three bytes in the set of space bytes but then other
characters that use these bytes such as Ƌ [c6, 8b] would also be
treated as at least partially spaces for word movement purposes.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---