Re: Some css issues in org-export

[Sebastian Rose <sebastian_rose@gmx.de>]

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