cocoaforge

I'm working on a message style, started from scratch because the code of my earlier created/adapted style is absolute crap So I decided to rewrite the entire code.

But, there's a real strange thing going on and I want to know wether someone has had this issue too:
This is what the html looks like in safari:


But in Adium, it gives me


Even the tutorial goes wrong (already when I put in the first piece of CSS)
Someone else had this problem and knows how to solve it?

The only thing you can really do, AFAIK, is design the style to display correctly in Adium, but not in Safari. Tweak you positioning and margins by looking at how Adium displays it.

Son of a Preacher Man wrote:The only thing you can really do, AFAIK, is design the style to display correctly in Adium, but not in Safari. Tweak you positioning and margins by looking at how Adium displays it.

Damn Is there a way to reload the theme while adium is stil running? 'couse everytime I adapt the theme, Adium remembers the previous style.

Nope. It's a bugger. When I'm testing message styles I generally set Adium to not sign me in on launch, otherwise I get angry messages...

If you hold down option while launching Adium, you can manage users for it. Add a new user without any accounts and use that for testing. Going one step further, if you create a duplicate of Adium.app, you can have your normal user signed in with the normal version of Adium and do testing with your no accounts profile in the copy of Adium. It's little bit of a hassle, but it should make testing a little quicker.

How does the tutorial 'go wrong'? (As its author, I'd like to know if it's a bug in the example code...)

Are you sure that the HTML as you have it in youre test file (for Safari) is the same as what ends up in Adium? I might try giving everything borders, so you can make sure it's at least nesting/structured right.

Perez wrote:Are you sure that the HTML as you have it in youre test file (for Safari) is the same as what ends up in Adium?

That is a very good point. Remember if you change any of the HTML files, you'll need to update the file you're feeding Safari, too.

I always used the same code in the content files as in the sample file.

BUT I HAVE THE SOLUTION

It's a bug in adium (I guess)

In the tutorial, the vim is used as text editor (and its great, I use it all the time) But it happens that I use DreamWeaver as HTML/CSS editor.

The end of line character is default the Macintosh CR only. THAT is the cause of the problems. If you change it to LF (Vim uses LF as default EOL), then... THERE ARE NO PROBLEMS!

Why does safari do this good: it recognizes LF, CR, CRLF as EOL, but it seems Adium doesn't.

Very odd! Weird, since Webkit drives both of them (right?), and since whitespace is irrelevant in HTML/CSS....

I remember this cropping up in someone's .plist for a sound set (or something); maybe the problem is when Adium's reading the file, not when it's being parsed by webkit. Anyway, good to know it's found.

Perez wrote:Very odd! Weird, since Webkit drives both of them (right?), and since whitespace is irrelevant in HTML/CSS....

I remember this cropping up in someone's .plist for a sound set (or something); maybe the problem is when Adium's reading the file, not when it's being parsed by webkit. Anyway, good to know it's found.

Look at any file with CR in pico or vim or whatever and you'll see "^M" for every newline.