emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode CSS property export bug
Date: Fri, 23 Apr 2010 11:07:25 +0200	[thread overview]
Message-ID: <8739ymedv6.fsf@gmx.de> (raw)
In-Reply-To: <E863A5F3-07D6-4D36-8505-76B3A27D125B@gmail.com> (Carsten Dominik's message of "Fri, 23 Apr 2010 08:30:33 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Apr 23, 2010, at 3:51 AM, Rick Moynihan wrote:
>
>> On 22 April 2010 22:29, Sebastian Rose <sebastian_rose@gmx.de> wrote:
>>> Rick Moynihan <rick.moynihan@gmail.com> writes:
>>>
>>> Hey Rick,
>>>
>>> interesting observation! I found, the pages validate everywhere, and so
>>> I started to search. It seems to be valid CSS 2 (I couldn't find a
>>> evidence though).
>>
>> Looks like an inconsistency in the W3C specs, as it appears to be
>> invalid (or absent from) the CSS selector spec, if not elsewhere.
>>
>> http://groups.google.com/group/jquery-en/msg/ca6ecd94ad4a23bd
>>
>>> Opera and firefox know how to handle that:
>>>
>>>
>>> h3[id="sec-1.1"]
>>> {
>>>  background-color:yellow;
>>> }
>
> We could change . to _ , but that would break old links, so I am hesitating.
> But of course if this really violates standards, we can change it.
>
> Sebastian has the last word on these issues.


* Links

  How many links like that will exist?
  Only links from external sites will break.
  I found one section link, but that's "sec-1"  (on de.wikipedia.org)

  Most links to certain sections use those custom IDs I guess.

* org-info.js

  I would then add the underscore to the regexp in org-info.js.
  People who use that will have to upgrade, too.


* Are there more modules involved??

sh$ grep -Fr sec- .
 org-docbook.el:(defcustom org-export-docbook-section-id-prefix "sec-"
 org-exp.el:			(format "sec-%s" (org-section-number level))))
 org-html.el:				(setq href (format "sec-%s" snumber))
 org-html.el:	(setq href (cdr (assoc (concat "sec-" snumber) org-export-preferred-target-alist)))
 org-html.el:	(setq href (or href (concat "sec-" snumber)))
 org-latex.el:		  (sec-depth (length org-export-latex-sectioning)))
 org-latex.el:	      (if (> hl-levels sec-depth) sec-depth hl-levels))))



Let's do it.

You don't want people to point on orgmode saying "They don't even use
valid CSS-IDs", do you?

And I guess most of us users will just be fine with it.



      Sebastian


> - Carsten
>
>>>
>>
>> Nice to know how to reference it.
>>
>> Cheers,
>>
>> R.
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> - Carsten
>
>

  reply	other threads:[~2010-04-23  9:07 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 [this message]
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

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=8739ymedv6.fsf@gmx.de \
    --to=sebastian_rose@gmx.de \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).