[css-d] Relative paths for images not working

2010-01-17 Thread Karl Bedingfield
Hi all, Having a little problem with image paths. I want to use: .header h2 a { background: url(/library/images/linkArrow.gif) right no-repeat; } but this does not work. But when I use the following below, it does work. .header h2 a {

Re: [css-d] Relative paths for images not working

2010-01-17 Thread G. Sørtun
Karl Bedingfield wrote: Having a little problem with image paths. [...] My folder structure is: library folder holds css folder and images folder. Since css folder and image folder are in same folder, try the short and direct... .header h2 a { background:

Re: [css-d] Relative paths for images not working

2010-01-17 Thread David Dorward
2010/1/17 Karl Bedingfield k...@bedingfield.biz:                background: url(/library/images/linkArrow.gif) right no-repeat; this does not work. But when I use the following below, it does work.                background: url(../../library/images/linkArrow.gif) right no-repeat; What

[css-d] table or not to table, was 4 part question about lining up boxes

2010-01-17 Thread Lisa Frost
Thanks for all the replies concerning the previous thread. I have been trying out some of the css from some of the references suggested and having some sucess. What started me thinking though was Georg's last suggestion that this type of information would be suitable for a table if time is tight,

Re: [css-d] table or not to table, was 4 part question about lining up boxes

2010-01-17 Thread David Laakso
Lisa Frost wrote: What started me thinking though was Georg's last suggestion that this type of information would be suitable for a table... Thanks in advance. Lisa At this time, with the particular situation at hand, Georg's suggestion might be best for the software, the client,

Re: [css-d] [OT] RE: u/u - why did it have to die?

2010-01-17 Thread Bob Rosenberg
At 13:23 -0800 on 01/15/2010, Thierry Koblentz wrote about Re: [css-d] [OT] RE: u/u - why did it have to die?: I don't agree. RADAR is an acronym because you're not supposed to spell the letters. CPU is an initialism, because you are supposed to spell the letters. Considering CPU (or else) as

Re: [css-d] [OT] RE: u/u - why did it have to die?

2010-01-17 Thread Chris F.A. Johnson
On Sun, 17 Jan 2010, Bob Rosenberg wrote: At 13:23 -0800 on 01/15/2010, Thierry Koblentz wrote about Re: [css-d] [OT] RE: u/u - why did it have to die?: I don't agree. RADAR is an acronym because you're not supposed to spell the letters. CPU is an initialism, because you are supposed to

Re: [css-d] [OT] RE: u/u - why did it have to die?

2010-01-17 Thread Theresa Mesa
I do believe Eric himself shut this conversation down a couple of days ago. It's not in any way related to CSS. Theresa On Jan 17, 2010, at 12:45 PM, Bob Rosenberg wrote: At 13:23 -0800 on 01/15/2010, Thierry Koblentz wrote about Re: [css-d] [OT] RE: u/u - why did it have to die?: I

Re: [css-d] [OT] RE: u/u - why did it have to die?

2010-01-17 Thread Rob Emenecker
Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced determines where an Acronym is also an Initialism.

Re: [css-d] [OT] RE: u/u - why did it have to die?

2010-01-17 Thread Rob Emenecker
You're right. Sorry. He did. Rob Emenecker @ Hairy Dog Digital www.hairydogdigital.com Please note: Return e-mail messages are only accepted from discussion groups that this e-mail address subscribes to. All other messages are automatically deleted.

Re: [css-d] [OT] RE: u/u - why did it have to die?

2010-01-17 Thread Chris F.A. Johnson
On Sun, 17 Jan 2010, Rob Emenecker wrote: Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced