freenode/#clim - IRC Chatlog
Search
6:23:48
loke
The problem is that if you have a sequence of characters, abcdef (where the letters represrnts unicode codepoints), you may have abc representing one symbol, d representing another etc... Also, if you have two symbols ab, then in some writing systems the sape of b depends on what character a is.
6:26:16
loke
A grapheme cluster is basically the thing that sits in a single "box" in an editor when you're eidting monospace text
6:28:01
loke
You always map multiple code points to a visual element. That's what is called a grapheme cluster. Then there is anothe rlayer of replacement happening at font shaping time.
6:29:06
beach
I am saying that you might want separate display modules for the same contents, and one of them might be that you just want to display each code point separately, so that it is obvious what the contents of the buffer is.
6:29:47
beach
With Cluffer, each display module must contain a copy of the buffer contents (as it was when the display module asked for it) anyway.
6:29:47
loke
Actually, that's what I'm doing. We might actually be talking about the same thing, but referring to diffeenrt layers.
6:33:33
loke
Anyway, this is just an experimental project, so I am goin o ignore nay issues with lines linger than, say, 1000 character.
15:11:35
ck_
beach: how does it fail? I think the best course is to check whether *truetype-font-path* contains some of the fonts it needs first.
15:19:05
beach
It fails with a condition being signaled, and the condition reporter said: McCLIM was unable to configure itself automatically using fontconfig. Therefore you must configure it manually.
15:22:53
loke
beach: By the way, I just realised that I can't actually cache the fline height in the LINE instance... Because the you can have the same buffer showing in mltiple panes, each with a different font. So the cache has to be linked to the frame, not the buffer
15:23:59
beach
Component #:CL-FREETYPE2 not found, required by #<SYSTEM "mcclim-fonts/clx-freetype">
15:35:17
ck_
beach: then I don't understand what the problem is, sorry. When I encountered that problem (when I first ran mcclim), I saw the same warning, spawned by warn-about-unset-font-path in extensions/fonts/fontconfig.lisp
15:39:08
loke
Then I have no idea. Might be something with asdf. Never heard abou anyone having that problem, but then again, I think almost everybody uses QL
15:39:55
loke
Of course, but it's the discussion we've had previously. There simply isn't any pure Lisp alternative to Fontconfig, Freetype or Harfbuzz.
15:42:08
beach
What I really want to do is to configure the font stuff manually, as per the first message.
15:45:04
ck_
I believe that you set mcclim-truetype:*families/faces* to a plist of entries like ((:serif :roman) . #P"/Path/to/A Roman Font.ttf")
15:45:19
jackdaniel
loke: our implementation *is* such alternative in pure lisp. you may point many disadvantages (i.e shaping), but it doesn't make it a "nonalternative" -- especually that nomen omen mostly used language is Engliah