Re: Editor component

On 2007-02-15, Hans-Peter Diettrich <DrDiettrich1@xxxxxxx> wrote:

(license MPL-LGPL)
No problem, so far. I've implemented the base classes almost from
scratch, so that I think that I'm not bound to any license myself, on
that part.

It usually is no problem, when done early on. Only when you have received
non-trivial patches under MPL-only it becomes a problem. This is a major
problem for incorporating Jedi source. (except Jedi Api lib, where Marcel
van Brakel, who owned the bulk of the sources was so kind to relicense)

Btw, I saw your Unicode wish, are you planning to avoid widestring? This
due to the relative slowliness under Delphi (as opposed to e.g. Kylix, where
it is ref counted, but not COM).

The display string type is subject to conditional compilation. I already
had a discussion about the implementation of Unicode, and FreePascal
seems to vote for UTF-8.

Mostly yes. Since everything but Windows banks on UTF8, and starting with
XP, it is not a problem anymore on Windows too. (parts are backportable to
win2000 even afaik)

I for my part wanat to use WideStrings and TextOutW, because they allow
for a simplified handling of tab expansion and character substition in the
visualization of whitespace and control characters.

Why is it simplified? For proper unicode support, you still have to look out
for surrogates with a 2 byte system?

Speed should not matter in the GUI, and the storage of the text is not
affected, as long as the text for a line can be retrieved in the display
string type.

Agreed. Lowlevel operations on your buffer could be done in pwidechar.

I hear people so often ask for more "Unicode" support in Delphi, and
since an editor of course is affected by such support, I'd like to hear
what they really miss?

From what I see on FPC bugreports, simply the ability to comment in their
own language (read: native character set), without going to constant
character sets conversions, and workarounds, iow the ability to do anything unicode
without additional effort. Sometimes also to use e.g. identifiers with non
A..Z chars in them.

With regards to an source code editor, the compiler and his acceptable
file formats comes into play. Most compilers will accept Unicode only
inside string literals, and possibly in comments.

Beauty of UTF8, makes them easy to skip.

Newer Delphi versions can process UTF-8 source files, but other compilers
are more restrictive, and will require an ASCII replacement for non-ASCII
characters. Because I'm not familiar with international issues, like IMO
and right-to-left entry of text, my basic controls leave all that to
derived classes.

I don't think right to left entry is a requirement for source editor. Only if
you want to broaden the scope that would be.

.

Relevant Pages

  • Re: VB - Ascii to Unicode and then Unicode to UTF-8 conversion (Very desperate!!)
    ... Latin together) then you have to use a Unicode column type. ... AscW returns the real Unicode character ... for Chinese characters, ... then the next thing to worry about is your CSV file. ...
    (microsoft.public.vb.general.discussion)
  • Re: Unicode Support
    ... if two Unicode strings are the same? ... UTF-16 is basically telling everyone "ok we all got to start ... character, and will likely support *both* endians. ... UTF-8 encodings are also easy to learn to ...
    (alt.lang.asm)
  • Re: Determining if a string is Unicode
    ... there's nothing magic about Unicode. ... where each character occupies 2 bytes, as opposed to a Single-Byte Character ... You could load up a string with rubbish, ... > INF file like so: ...
    (microsoft.public.vb.general.discussion)
  • Re: KANJD212
    ... >>Who decides the factors and what are their criteria, Unicode? ... But once a character is defined/get a codepoint in Unicode it ... standard modifies the codepoint of the kanji to a totally new ... I can use a code like JIS X0208 along with a font ...
    (sci.lang.japan)
  • Re: Enhanced Unicode support for "Go" tools
    ... the point to remember is that UNICODE is a _character ... It's the fonts, the OS and the application which work together ... society for the protection of French from English ...
    (alt.lang.asm)