On 10/30/2016 06:15 PM, Lars wrote:
Off topic, off list, but..
--
TRUTH in her dress finds facts too tight.
In fiction she moves with ease.
Stray Birds by Rabindranath Tagore
What does this mean?
Something about this:
http://www.the-niceguy.com/articles/Nutballs.html
The only thing I can
On 10/22/2016 06:25 AM, Juha Manninen via Lazarus wrote:
On Sat, Oct 22, 2016 at 4:12 AM, Martin Frb via Lazarus
wrote:
Which ones does it not support?
When I added it to SynEdit it was complete. It had all the combinings that
the utf8 standard had back then. (at
On 24.10.2016 15:09, Mattias Gaertner via Lazarus wrote:
These functions exist.
This of course is great (while the lack of documentation supposedly
makes them hard to use).
In fact I am not asking, but the question is part of the OP's problem.
And here I wanted to point out the ambiguity of
On Mon, 24 Oct 2016 14:35:28 +0200
Michael Schnell wrote:
>[...] but even trying to find out a very short information is identical is not
decently possible.
>[...]
> I meant to point out exactly this ambiguity:
>
> identically coded vs. identically looking (e.g. combining
On 24.10.2016 13:34, Mattias Gaertner via Lazarus wrote:
That depends on what you mean with "identical".
You are absolutely right. Very sorry for being critical while being
vague myself (again typing faster than thinking) ;) .
I meant to point out exactly this ambiguity:
identically coded
On 23.10.2016 11:31, Jürgen Hestermann via Lazarus wrote:
But Unicode should have cared.
It was made for its use on computers.
I don't think so.
I suppose it was defined top allow for printing out digital documents in
mind, but not with working with them.
At least this i what the outcome
On 21.10.2016 12:05, Gabor Boros via Lazarus wrote:
2016. 10. 21. 10:25 keltezéssel, Juha Manninen via Lazarus írta:
* Please read the wiki page ...
I read, I read but if contains buggy example... ;-)
I need a quick and a rock solid solution.
AFAIK, the only decent advice is never to use
On Sun, 23 Oct 2016 11:31:00 +0200
Jürgen Hestermann via Lazarus wrote:
> Am 2016-10-22 um 22:38 schrieb Mattias Gaertner via Lazarus:
> > Languages don't care about programmers.
>
> True.
> But Unicode should have cared.
> It was made for its use on computers.
Am 2016-10-22 um 22:38 schrieb Mattias Gaertner via Lazarus:
> Languages don't care about programmers.
True.
But Unicode should have cared.
It was made for its use on computers.
Pressing each and every language peculiarity
into Unicode was a mistake and
made Unicode so hard to use.
--
On Sat, 22 Oct 2016 13:25:30 +0300
Juha Manninen via Lazarus wrote:
>[...]
> I guess the biggest complexity is in glyphs and ligatures. I still
> don't understand their details.
There is nothing to understand. Some languages have irregular letters.
Same as English
On Sat, 22 Oct 2016 12:13:04 +0200
Jürgen Hestermann via Lazarus wrote:
> Am 2016-10-22 um 10:53 schrieb Mattias Gaertner via Lazarus:
> > Maybe you mean ligatures? Many languages have them, even German:
> > https://en.wikipedia.org/wiki/Typographic_ligature
>
On Sat, Oct 22, 2016 at 1:13 PM, Jürgen Hestermann via Lazarus
wrote:
> So ligatures should not influence string encoding in FPC.
> Or am I missing something here?
I guess it matters for a text layout software. It should not separate
the two characters forming a
On Sat, Oct 22, 2016 at 4:12 AM, Martin Frb via Lazarus
wrote:
> Which ones does it not support?
> When I added it to SynEdit it was complete. It had all the combinings that
> the utf8 standard had back then. (at least that I could find in the
> documentation)
>
>
Am 2016-10-22 um 10:53 schrieb Mattias Gaertner via Lazarus:
> Maybe you mean ligatures? Many languages have them, even German:
> https://en.wikipedia.org/wiki/Typographic_ligature
I thought that ligatures are just a matter of the font
but not the unicode representation?
When I write a text
On Sat, 22 Oct 2016 02:12:34 +0100
Martin Frb via Lazarus wrote:
>[...]
> It is my understanding (but I do not know for sure) that in some
> languages (such as Arabic) certain letter combinations form a single
> glyph (afaik/google see
On 21/10/2016 22:16, Juha Manninen via Lazarus wrote:
UTF-16. It does not support all the complex rules of combining
CodePoints, but it apparently works well for accented characters in
western languages.
Which ones does it not support?
When I added it to SynEdit it was complete. It had all
On Fri, Oct 21, 2016 at 2:26 PM, Juha Manninen
wrote:
> No, neither FPC nor Lazarus have library code to deal with [combined
> CodePoints] yet.
> The goal is to have an enumerator for user perceived characters, just
> like LazUnicode unit has for encoding agnostic
On Fri, Oct 21, 2016 at 5:08 PM, Jürgen Hestermann via Lazarus
wrote:
> And again we are at the point where you need to understand what goes on
> under the hood... ;-)
Yes but that is true with any programming.
I am truly happy that we have Unicode instead of the
Am 2016-10-21 um 13:23 schrieb Gabor Boros via Lazarus:
> I will know if somebody describe what a difference between á and an á
characters in two points of my program.
The problem is, that Unicode has a code point for "á" but
also allows to compose this characters by having an "a"
and an "´"
2016. 10. 21. 12:38 keltezéssel, Juha Manninen via Lazarus írta:
for i:=1 to UTF8Length(s) do Write(UTF8Copy(s,i,1))
No, it not a good solution!
I predict that most your code can still use byte indexing. At some
point you will get a Heureka-moment like "hey, I don't need the
codepoint index
On Fri, Oct 21, 2016 at 2:13 PM, Gabor Boros via Lazarus
wrote:
> Same FCP same Lazarus. Why is there a difference in the result?
You still did not read the wiki page:
http://wiki.freepascal.org/Better_Unicode_Support_in_Lazarus
Console programs are mentioned in
On Fri, Oct 21, 2016 at 12:51 PM, Lars via Lazarus
wrote:
> Indeed this is a serious problem these days, unicode.. which is almost a
> virus.
> In GoLang they use something called "Runes" to try and solve the problem.
I had to search about what "runes" in GoLang
2016. 10. 21. 12:48 keltezéssel, Jürgen Hestermann via Lazarus írta:
If you realy need the character position/length, then
you have to use UTF8Length/UTF8Copy/etc.
But as said: It is only needed in special circumstances.
Still you have to know when to use what.
I will know if somebody describe
On Fri, October 21, 2016 1:03 am, Gabor Boros via Lazarus wrote:
> Hi All,
>
>
> In the past I used Length, Pos, Delete, for i:=1 to Length(s) do s[i]...
> and realized yesterday these practices are wrong. But I do not know what
> the right practice.
Indeed this is a serious problem these days,
On Fri, 21 Oct 2016 11:29:36 +0200
Gabor Boros via Lazarus wrote:
> 2016. 10. 21. 10:24 keltezéssel, Juha Manninen via Lazarus írta:
> > A "character" in Unicode is an ambiguous term.
> > Often the good old byte (codeunit) access is very useful.
> > See:
> >
25 matches
Mail list logo