emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode CSS property export bug
Date: Fri, 23 Apr 2010 17:25:48 +0200	[thread overview]
Message-ID: <BD1AB556-B0F5-4AE2-B822-138A54FCF8C3@gmail.com> (raw)
In-Reply-To: <877hnycuqf.fsf@gmx.de>


On Apr 23, 2010, at 12:46 PM, Sebastian Rose wrote:

> Rick Moynihan <rick.moynihan@gmail.com> writes:
>> As far as I can see there are three options.
>>
>> 1) Use underscores (against the above advice) (practically probably
>> not a huge issue) e.g. outline-container-1_1
>> 2) Overload the use of hyphens to be for both spaces and .'s...  e.g
>> outline-container-1-1
>> 3) Stop using hyphens for spaces and switch to camel case convention,
>> freeing hyphens to be substitutes for .'s e.g. outlineContainer1-1.
>> This option seems like the best design, though it completely blows
>> backwards compatability away so is probably a non-starter.  Leaving  
>> us
>> with 1) or 2).
>>
>> Personally I think *if* underscores aren't a problem for modern
>> browsers, ie8, firefox 3.5+, recent opera's safari and chrome we use
>> them.
>
> Allright then.
>
>
> He says:
>
>  "Internet Explorer 6 for Windows, published after the errata, permits
>   underscores and escaped underscores."
>
> So do IE4x and IE5x.
> Internet Explorer seems not to be the problem? IE7+ anyone?
>
>
>   "Opera 3.x through 5.x does not recognize underscores or escaped
>   underscores, and so acts the same as Navigator 4.x in this regard."
>
> Very old browsers. Do we have to support them?


I don't think so.

- Carsten

>
>
>
> The appended testfile works in Opera10 an FF 3.6. Is there something
> missing?
>
>
>
>   Sebastian
>
>
> <test.html>

- Carsten

      parent reply	other threads:[~2010-04-23 15:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 17:38 org-mode CSS property export bug Rick Moynihan
2010-04-22 21:29 ` Sebastian Rose
2010-04-23  1:51   ` Rick Moynihan
2010-04-23  6:17     ` Sebastian Rose
2010-04-23  6:30     ` Carsten Dominik
2010-04-23  9:07       ` Sebastian Rose
2010-04-23 10:01       ` Rick Moynihan
2010-04-23 10:46         ` Sebastian Rose
2010-04-23 11:00           ` Rick Moynihan
2010-04-23 12:22             ` Rick Moynihan
2010-04-23 15:24               ` Carsten Dominik
2010-04-23 12:29             ` Richard Riley
2010-04-24  0:14             ` Carsten Dominik
2010-04-24  8:58               ` Sebastian Rose
2010-04-24 11:25                 ` Sebastian Rose
2010-04-24 12:23                   ` Carsten Dominik
2010-04-24 12:42                     ` Sebastian Rose
2010-04-24 15:36                   ` Carsten Dominik
2010-04-25 10:27                     ` Sebastian Rose
2010-04-25 12:08                       ` Carsten Dominik
2010-04-26  9:46                         ` Rick Moynihan
2010-04-23 15:25           ` Carsten Dominik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BD1AB556-B0F5-4AE2-B822-138A54FCF8C3@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian_rose@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).