Yes, many fonts have the glyphs included in "Box drawing" and "Block elements" (Unicode 9472-9727), but the .nfo file expects those glyphs to reside inside "Latin-1 Supplement" (Unicode 0080 to 00FF) and if they don't, they don't show up.
The font "Lucida Console P" can correctly render the special characters needed in Latin-1 Supplement.
This is the way a correctly .nfo file should end up looking like:
I don't know if this is a success, but I'll copy-paste some nfo content as it looks with Monaco font. Might work, might not.
ßÛÛ²°°°²²° ÜÞÛ²²²²²²Û ßÛÛ²°°²ÛÛ ß° °²Û ßÛ²°° °²ÛÛ °²ÛÛ ÛÛ²°²ÛÝ
ÞÛÛ²°°°° ÛÛ ÛÛ²°°°°²ß ÞÛ²°°°²ÛÛÛ °°ß ÞÛ²° °²ÛÛ °²ÛÛÜ ÛÛ²°°²ÛÛ
ÛÛ²°° ° ÛÛ²Û ÛÛ²°° ° ÛÛ²° °²²ÛÛ ÜÛÛ²° °°²ÛÝ °²ÛÛÛÛ²°°²ÛÛÝ
ÞÛÛ° Û²²ÛÛ Û²° ÛÛ²° °²²ÛÜ ÜÜÛ²²° °²ÛÛ ÛÜ°²ÛÛ²° °²ÛÛ
Off-course, I could continue to use "Lucida Console P" for all Textmate purposes, but thats not optimal.
/ Johan
On 8 okt 2006, at 07.16, Jacob Rus wrote:
Jacob Rus wrote:
I bet you could make a command which would change these code points into the relevant unicode code points, so that your artwork would show up correctly. The nice thing about unicode is it can handle all of these glyphs. I bet you could even use some existing command line tool like iconv to do it.
Then as your font you can use DejaVu Sans Mono, which has all of these unicode glyphs included (I just checked).
-Jacob
______________________________________________________________________
(threading gets destroyed and the universe will collapse if you don't)
----------------------------------------------------------------------
Johan Klintberg
Kopparmöllegatan 14
254 36 Helsingborg
Phone: +46 (0)42 - 210 214
Cell: +46 (0)709 - 37 89 89
______________________________________________________________________
(threading gets destroyed and the universe will collapse if you don't)