Clients like Fire and Gaim interact oddly with tik.
They have a tendency to produce messages far too small
to read. That is, they'll come across in 3 or 4 point
font. Which is unreadable. My current workaround is
to tail -f ~/.tik/capture/buddy the person involved and
have a terminal open, but that's really annoying.
There are font tags in the logs like <P>02:40:34
Name_Deleted: <FONT SIZE="4"><FONT FACE="arial"><FONT
FACE="arial">how's this?</FONT></FONT></FONT></P> my
guess is that they're using the normal way to use a
FONT tag in HTML which is to use relative size. so 3
is normal, 4 is big, 5 is huge, but TiK interprets it
as 4pt font, 3pt font, etc.
I don't know how to fix this myself but i can't believe
it's hard .. .
Logged In: NO
The actual problem comes down to this:
The client is sending 2 font size tags, which confuse TIK. I do
not know TCL well enough to fix it myself, but that seems to
be the problem... there are nested fonts.
It's not just GAIM. Some aim clients send that as well.
The best thing I can say for now is to turn off font sizes, then
reopen their window, then turn font sizes back on.
Their window won't show font sizes, because the settings are
copied each time a new window is opened.
I'm not an official maintainer of TIK, but I promise once I
learn TCL that I will try to keep it up.
Hope this workaround "fixes" your problem.
Lothsahn
Logged In: NO
The actual problem comes down to this:
The client is sending 2 font size tags, which confuse TIK. I do
not know TCL well enough to fix it myself, but that seems to
be the problem... there are nested fonts.
It's not just GAIM. Some aim clients send that as well.
The best thing I can say for now is to turn off font sizes, then
reopen their window, then turn font sizes back on.
Their window won't show font sizes, because the settings are
copied each time a new window is opened.
I'm not an official maintainer of TIK, but I promise once I
learn TCL that I will try to keep it up.
Hope this workaround "fixes" your problem.
Lothsahn