Text 17578, 75 rader
Skriven 2015-04-03 19:21:46 av Nicholas Boel (1:154/701)
  Kommentar till text 17571 av Alan Ianson (1:153/757)
Ärende: Re: I read it wrong
===========================
Hello Alan,

On 02 Apr 15 16:27, Alan Ianson wrote to Nicholas Boel:

 NB>> Mystic itself doesn't support UTF-8 out of the box. So that's
 NB>> most likely where your problem lies.

 AI> No, the problem is my terminal (well, it's all a little bigger than
 AI> that) of choice. ATM, I'm running arch and I can't seem to get high
 AI> ascii support. Oddly I do get high ascii support with xfce4-terminal
 AI> but it doesn't work well. You run arch don't you? Do you have high
 AI> ascii support on your terminal? Even if I can't or don't have high
 AI> ascii I'm hoping to convert at least those files that contain high
 AI> ascii to utf-8 in the hopes that I can use high ascii with a utf-8 or
 AI> not terminal. I think at the end of the day utf-8 is what we need.

 AI> On this slackware box I'm on now I have no trouble with high ascii,
 AI> everything Mystic displays looks the way it should. Maybe I need to do
 AI> something different for arch I'm not sure.

Yes I can support ANSI in both of my Linux terminals, Gentoo and Arch, while
using UTF-8. I choose between two different fonts in a UTF-8 only terminal
using the "terminus-fonts" package.

setfont ter-i14b = Supports 256 glyphs and keeps the ansi "blocks" in the
correct translation.
setfont ter-v14b = Supports 512 glyphs and is used for UTF-8 only. It will not
display ANSI properly though without a script that remaps those ansi blocks.

So, reset your terminal and set your font:

$ reset
$ setfont ter-i14b

then you can see if it works by loading up mystic's configuration program:

$ ./mystic -cfg

Should display properly. Then if/when you want to go back to a purely UTF-8
console, just reset again and use the other font.

If you don't care to install terminus fonts, you should be able to use the
'default-8x16' font to see ansi properly as well.

 NB>> As for reading/writing messages in
 NB>> UTF-8, you could easily setup Golded with an external editor
 NB>> (nano or vim have been tested in this realm so far, by myself and
 NB>> Maurice) which will not let you read UTF-8 in Golded, but once
 NB>> you load the message up in the external editor it will display
 NB>> perfectly. Writing in UTF-8 would obviously work as expected
 NB>> since you're using an editor that supports UTF-8, of course.

 AI> Golded is on my todo list :) I've seen that mutil can output an
 AI> areas.bbs so that will take care of the area config. I have downloaded
 AI> it but haven't done the setup yet.

Actually, while working with James/g00r00 on Mystic updates and testing and
whatnot. I noticed some oddities with Golded using Mystic's message bases.
After James took a look at it and installed Golded himself, you can now use
Golded on your Mystic message bases directly without issue.

 AI> On the other hand I'm very comfortable reading/writing messages from
 AI> the BBS. One thing I miss is taglines. I know golded has them but JC
 AI> was talking about adding support for taglines to mystic so it may come
 AI> to pass one day.. :)

Very possible. After the 1.10 release I'm fairly sure he's taking an extended
break from Mystic, as he worked his butt off through the 1.10 development. But
when he returns, he has mentioned a bunch more ideas for 1.11. :)

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
 * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)