From: Sebastian Rose <sebastian_rose@gmx.de>
To: Rustom Mody <rustompmody@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Some css issues in org-export
Date: Mon, 02 Feb 2009 10:15:57 +0100 [thread overview]
Message-ID: <877i49nqr6.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <f46c52560902020020i1ea8ee8dgf902b6d2adf2207d@mail.gmail.com> (Rustom Mody's message of "Mon, 2 Feb 2009 13:50:00 +0530")
Hi,
Seems there are some regressions/new issues. XHTML-validity is a moving
target and someting to re-work from time to time.
It's actually quite seldom I have these problems with the current
version.
I only found this one on the first glance:
* <div> is _not_ allowed in <p>
=> --->8----------------------------->8----------------------------->8---
* Produkt Attribute
[[file:../img/osCommerce-products-attributes.png]]
more text
<= ---8<-----------------------------8<-----------------------------8<---
becomes
=> --->8----------------------------->8----------------------------->8---
<div id="outline-container-1" class="outline-2">
<h2 id="sec-1">1 Produkt Attribute </h2>
<div id="text-1">
<p>
<div class="figure">
<p><img src="../img/osCommerce-products-attributes.png" alt="../img/osCommerce-products-attributes.png" /></p>
</div>
</p>
<= ---8<-----------------------------8<-----------------------------8<---
* Also I found some more, but they where homegrown
I had this in my configuration file:
(setq org-link-abbrev-alist
'(("man" . "http://localhost/devel/man.php?q=man&what=%s")
("info" . "http://localhost/devel/man.php?q=info&what=%s")
("wikipedia-en" . "http://en.wikipedia.org/wiki/%s")))
Note the ampersands in `man' and `info'! This is no valid XHTML!
Hence I had to change all apersands to `&' like this:
(setq org-link-abbrev-alist
'(("man" . "http://localhost/devel/man.php?q=man&what=%s")
("info" . "http://localhost/devel/man.php?q=info&what=%s")
("wikipedia-en" . "http://en.wikipedia.org/wiki/%s")))
Please post the errors you get here, so we all can hunt them when we
find time for it.
I use http://validator.w3.org/ (press CTRL-SHIFT-A in Firefox to
validate local HTML) and the error messages are quite clear.
Regards,
Sebastian
Rustom Mody <rustompmody@gmail.com> writes:
> I tried validating this at http://validator.w3.org/
> and its not valid XHTML.
>
> Dont know more HTML to comment :-)
>
>
> On Mon, Jan 19, 2009 at 8:43 PM, Sebastian Rose <sebastian_rose@gmx.de> wrote:
>> Hi Rustom,
>>
>>
>> "Rustom Mody" <rustompmody@gmail.com> writes:
>>> On Mon, Jan 19, 2009 at 6:29 PM, Sebastian Rose <sebastian_rose@gmx.de> wrote:
>>>>
>>>> Hm - we do not provide a special stylesheet for printing. But since
>>> <snipped>
>>>>
>>>> Maybe we should add this line to the very top of the document:
>>>>
>>>> <?xml version="1.0" encoding="utf-8" ?>
>>>
>>> I tried adding this by hand (using emacs) it made no difference to the printout
>>> The boxes show the digits like this:
>>>
>>> 0 0
>>> 2 0
>>>
>>> Also I noticed that emacs shows (Unix) in the modeline but it shows
>>> ^Ms at EOLs in the buffer.
>>>
>>> I understand too little of unicode etc to even claim that this is
>>> 'not-as-it-should-be' -- just mentioning it in case it gives any
>>> clues...
>>
>>
>> Hmmm. In the modeline I have either an `U' (for utf-8) or `1' or
>> iso-8859-1 and other single byte encodings. OrgMode seems to set the
>> charset correctly on export here. If I do a `save file as' in Firefox
>> and open it in emacs, I see the encoding is exactly what's in the line
>> with the `charset'. You should change the `utf-8' to what's in that line
>> with the `charset':
>>
>> <meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
>>
>> in case of
>> http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.php.
>>
>>
>> If you add the `<?xml....' line, make shure that
>> a) the encoding is the same as the one in the `charset' line and
>> b) the file is indeed written to disk using that encoding. See
>> `C-h k C-x RET f' or ust do `C-x RET f TAB TAB'.
>>
>>
>>
>> Anyway, I believe it's a question of your browsers configuration since
>> no one else has that problem.
>>
>>
>>
>> The line endings have nothing to do with encoding. Their bit-wise
>> representation is the same for all single byte encodings and utf-8.
>>
>>
>>
>> Good luck,
>>
>>
>>
>> --
>> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
>> Tel.: +49 (0)511 - 36 58 472
>> Fax: +49 (0)1805 - 233633 - 11044
>> mobil: +49 (0)173 - 83 93 417
>> Http: www.emma-stil.de
>>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.: +49 (0)511 - 36 58 472
Fax: +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http: www.emma-stil.de
next prev parent reply other threads:[~2009-02-02 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 12:04 Some css issues in org-export Rustom Mody
2009-01-19 12:27 ` Giovanni Ridolfi
2009-01-19 12:59 ` Sebastian Rose
2009-01-19 13:57 ` Rustom Mody
2009-01-19 15:13 ` Sebastian Rose
2009-02-02 8:20 ` Rustom Mody
2009-02-02 9:15 ` Sebastian Rose [this message]
2009-02-02 9:33 ` Sebastian Rose
2009-02-02 10:02 ` Rustom Mody
2009-02-02 11:09 ` Sebastian Rose
2009-02-02 11:20 ` Carsten Dominik
2009-02-02 12:03 ` Sebastian Rose
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=877i49nqr6.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=rustompmody@gmail.com \
/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).