libera/#commonlisp - IRC Chatlog
Search
18:09:42
scymtym
splittist: i see. i extended zpb-ttf to support opentype fonts but i'm apparently too slow to release
18:11:08
splittist
The Type2 charstring parsing just takes a bytestream and some defaults from the font, so should be usable in a OFF / OpenType context.
18:17:11
splittist
I guess I should put what I've got (which is not in any way release-worthy) somewhere you can pick the eyes out of it and get back to extracting text from PDFs (:
18:18:51
scymtym
i didn't mean to discourage you from working on fonts. but looking at your solution would definitely be interesting
18:20:55
scymtym
ACTION also started to add support for the color bitmap tables at some point: https://techfak.de/~jmoringe/format.opentype-color-bitmaps-1.png :)
18:30:17
splittist
scymtym: I've dumped what I have here: https://github.com/splittist/jqs-type1 . To treat everything as octets I have reader macros on #" and #! as analogues of " and #\ (so you can use the character(s) for their byte values).
18:50:51
beach
Filystyn: #commonlisp is not really meant for newbie questions, although they are tolerated to some extent.
18:51:52
beach
Filystyn: But seriously, you need to learn to read some relevant sections of the standard.
18:52:55
beach
Filystyn: I understand, but you are potentially wasting people's time by asking questions that could be asked with a simple lookup in the standard.
20:02:36
contrapunctus
ober: strange thing to say to someone who tirelessly and patiently answers the darnedest newbie questions in #clschool O_o
20:05:57
jackdaniel
I agree that Filystyn asks questions that they should have found answers on their own, but mind that at least in theory being helpful does not contradict scarying people off
20:06:15
jackdaniel
another thing worth mentioning that scarying some people off may be a good filter
22:33:07
jmercouris
I'm having a problem with format, if I do something like "(format t "~:[~;lol~]" "fish")" it will slurp fish, ,and I can't print it
22:33:52
jmercouris
of course I *could* write a function that does this, but that seems excessive, anyone know how to print nthe value of a variable, or otherwise nil?
22:34:13
jmercouris
(format "~magical_control_string" "tomato") -> tomato, (format "~magical_control_string" nil) -> nil
22:35:34
jmercouris
you know what, forget it, I'll just set it to a default value of "" and call it a day
22:39:25
semz
jmercouris: For the first issue, ~* goes to the next argument and ~:* goes to the previous one, without printing anything.
22:44:29
pjb
jmercouris: (list (format nil "~A" "tomato") (format nil "~A" nil)) #| --> ("tomato" "nil") |#
1:55:52
jeosol
is (room-values) http://www.lispworks.com/documentation/lw71/LW/html/lw-1426.htm#46961 availabe in sbcl, if so under what package. I asked in #sbcl, cross-posting here. thanks
5:45:05
jeosol
I think I may have memory leak in my long running application that seems to cause it to crash/restart the machine. I want to capture the output of (room) as the application is running (e.g., after each iteration) so I can create a time series for the different categories of space usage when (room) is called. is this reasonable?
5:56:42
pjb
jeosol: yes. The verbose output of ROOM is written on *standard-output* so you may want to redirect it to collect it in a single file. Unfortunately, the result is implementation dependent, so you cannot count on it to be meaningful.
5:58:12
jeosol
pjb: you are so right. I was using with-output-to-string, get the string, process it. Unfortunately, the output is ordered in decreasing order of the usage. My initial implementation was processing the parsed string line by line, and reading of the usage.
5:59:02
pjb
jeosol: that's a good idea, since you can then #+ the implementation of this parsing depending on the implementation, to return always the same value(s).
5:59:10
jeosol
pjb: Of course this is not robust and a particular category may be on a different line due to the usage for that category since (room) for sbcl the output are sorted in decreasing order of the usage. So I may have to resort to some regex or esrap
6:01:45
jeosol
The code base is large and I think implementing this usage time series will at least give me some idea of where to look at. When I started coding, I was just creating arrays on the fly and I wasn't being very discipline. For my design, I elected to use variables to hold all computations for my runs. So when the runs are done, no further
6:02:58
jeosol
Of course, this requires having a lot more variables. Another option, is write intermediate results to files, after the runs are done, have another code post-process the intermediate files and generate other statistics. I am thinking this latter option should have been the better one.