Re: Editor component



Marco van de Voort 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 why I don't like to include any license information into the source files. Legal and functional topics should be strictly separate.



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?

Unicode doesn't guarantee that a single display character is represented by a single code point. Therefore I intend to simplify things, and assume UCS-2 with 1 code point for 1 character. If somebody wants to implement a more sophisticated rendering, he can override all the related methods in a derived class. Then also proportional fonts may become acceptable, and more things, which are not required in an source code editor.


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.

The compatibility with other compilers doesn't leave room for exotic code pages in source code.


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.

Skip characters in string literals or identifiers? ;-)

DoDi
.



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)