Carsten Dominik writes:
> On Oct 25, 2010, at 11:52 PM, Baoqiu Cui wrote:
>
>> Sebastian Rose writes:
>>
>>> Carsten Dominik writes:
OK, I will use class. I could make a special case for the docbook
exporter..
>>>
>>> +1
>>
>> +1 for making a "special case for the docbook exporte
OK, I think this change is now done. Thank you all for sharing your
expertise!
- Carsten
On Oct 25, 2010, at 11:39 PM, Sebastian Rose wrote:
Christian Moe writes:
Maybe someone with a browser where colgroups actually do work
(Opera!) can check
1. if they only work with the align attribut
On Oct 25, 2010, at 11:52 PM, Baoqiu Cui wrote:
Sebastian Rose writes:
Carsten Dominik writes:
OK, I will use class. I could make a special case for the docbook
exporter..
+1
+1 for making a "special case for the docbook exporter". :-) (DocBook
documents can be rendered in differe
Sebastian Rose writes:
> Carsten Dominik writes:
>> OK, I will use class. I could make a special case for the docbook
>> exporter..
>
> +1
+1 for making a "special case for the docbook exporter". :-) (DocBook
documents can be rendered in different formats, some of which (like PDF)
may know
Christian Moe writes:
> Maybe someone with a browser where colgroups actually do work (Opera!) can
> check
>
> 1. if they only work with the align attribute, and not with CSS, and
>
> 2. whether they still work (take precedence) now that the individual cells are
> aligned with CSS for their class
[Veering off-topic, just to round off a discussion]
On 10/25/10 4:55 PM, Sebastian Rose wrote:
How refer to all right-aligned `td' elements in a certain tables without
some special attribute anyway.
Fair point. (In an ideal world, as long as the whole column is
right-aligned it should be en
Actually, I have one more question:
The exporter does now (in addition to setting classes for individual
fields)
Should this be classes instead of align attributes as well?
Thanks!
- Carsten
Maybe someone with a browser where colgroups actually do work (Opera!)
can check
1. if they on
Carsten Dominik writes:
> OK, I will use class. I could make a special case for the docbook
> exporter..
+1
>> Having to set /anything/ on each cell just to align a column is not optimal
>> either, but since some browsers don't honor colgroups, it's the most robust
>> way.
How refer to
On Oct 25, 2010, at 3:13 PM, Christian Moe wrote:
On 10/25/10 11:08 AM, Carsten Dominik wrote:
On Oct 25, 2010, at 10:51 AM, Christian Moe wrote:
On 10/25/10 6:36 AM, Baoqiu Cui wrote:
I am wondering if there
is any special reason to use "class" instead of "align". If not,
can we
change th
On Oct 25, 2010, at 3:13 PM, Christian Moe wrote:
On 10/25/10 11:08 AM, Carsten Dominik wrote:
On Oct 25, 2010, at 10:51 AM, Christian Moe wrote:
On 10/25/10 6:36 AM, Baoqiu Cui wrote:
I am wondering if there
is any special reason to use "class" instead of "align". If not,
can we
change th
On 10/25/10 11:08 AM, Carsten Dominik wrote:
On Oct 25, 2010, at 10:51 AM, Christian Moe wrote:
On 10/25/10 6:36 AM, Baoqiu Cui wrote:
I am wondering if there
is any special reason to use "class" instead of "align". If not,
can we
change the elisp code to use "align"?
I believe the "align"
Carsten Dominik writes:
>
> I am actually using right now:
>
> th.right { text-align:center; }
> th.left { text-align:center; }
> th.center { text-align:center; }
>
> because is seem right to me that a table header is centrally
> aligned even if the fields are lift or right aligned.
yes, s
On Oct 25, 2010, at 11:02 AM, Giovanni Ridolfi wrote:
Carsten Dominik writes:
I am actually using right now:
th.right { text-align:center; }
th.left { text-align:center; }
th.center { text-align:center; }
because is seem right to me that a table header is centrally
aligned even if t
On Oct 25, 2010, at 10:51 AM, Christian Moe wrote:
On 10/25/10 6:36 AM, Baoqiu Cui wrote:
I am wondering if there
is any special reason to use "class" instead of "align". If not,
can we
change the elisp code to use "align"?
I believe the "align" attribute is slated for obsoletion in HTML5
On 10/25/10 6:36 AM, Baoqiu Cui wrote:
I am wondering if there
is any special reason to use "class" instead of "align". If not, can we
change the elisp code to use "align"?
I believe the "align" attribute is slated for obsoletion in HTML5, on
the grounds that it's better handled by CSS.
ht
On Oct 23, 2010, at 9:28 PM, Sebastian Rose wrote:
Carsten Dominik writes:
I have now in the default style:
td, th { vertical-align: top; }
th.right { text-align:right; }
th.left { text-align:left; }
th.center { text-align:center; }
I am actually using right now:
th.right { text-a
Carsten Dominik writes:
> Baoqiu,
>
> (or any other users of the docbook exporter)
> I am not sure if the docbook format has suffered from this change,
> could you please run a few tests involving tables and report back?
Thanks for supporting this new feature. DocBook exporter does not
really s
Carsten Dominik writes:
> I have now in the default style:
>
> td, th { vertical-align: top; }
> th.right { text-align:right; }
> th.left { text-align:left; }
> th.center { text-align:center; }
> td.right { text-align:right; }
> td.left { text-align:left; }
> td.center {
Carsten Dominik writes:
>> How about this (line-wrapped for readability):
>>
>>
>>
>> 1
>> bar
>> text
>>
>>
>> instead of
>>
>>
>> 1
>> bar
>> text
>>
>>
>> ??
>>
>>
>> Combined with the ways to add IDs and classes to tables, we could then style
>> the
>> columns better.
>>
>> I would l
Carsten Dominik writes:
>> OK, found it. It was in my .emacs which I didn't use for ages...
>>
>> But:
>>
>> > />
>>
>> must be:
>>
>> > />
>>
>>
>> i.e. "" and "" have to occur only once each and
>> wrap the "" definitions.
>>
>> The after each "" happens only for the second
>> table.
>
> Hi
On Oct 22, 2010, at 9:37 PM, Sebastian Rose wrote:
Carsten Dominik writes:
On Oct 22, 2010, at 3:59 PM, Sebastian Rose wrote:
Carsten Dominik writes:
Hi Sebastian,
my guess would be that you have customized the td and th tags?
If yes,
please
reset the customization, you need the new
On Oct 22, 2010, at 9:30 PM, Sebastian Rose wrote:
Carsten Dominik writes:
On Oct 22, 2010, at 3:59 PM, Sebastian Rose wrote:
Carsten Dominik writes:
Hi Sebastian,
my guess would be that you have customized the td and th tags?
If yes,
please
reset the customization, you need the new
Carsten Dominik writes:
> On Oct 22, 2010, at 3:59 PM, Sebastian Rose wrote:
>
>> Carsten Dominik writes:
>>> Hi Sebastian,
>>>
>>> my guess would be that you have customized the td and th tags? If yes,
>>> please
>>> reset the customization, you need the new default values (which you then
>>>
Carsten Dominik writes:
> On Oct 22, 2010, at 3:59 PM, Sebastian Rose wrote:
>
>> Carsten Dominik writes:
>>> Hi Sebastian,
>>>
>>> my guess would be that you have customized the td and th tags? If yes,
>>> please
>>> reset the customization, you need the new default values (which you then
>>>
On Oct 22, 2010, at 3:59 PM, Sebastian Rose wrote:
Carsten Dominik writes:
Hi Sebastian,
my guess would be that you have customized the td and th tags? If
yes, please
reset the customization, you need the new default values (which
you then can
still modify).
Please check the variable
Carsten Dominik writes:
> Hi Sebastian,
>
> my guess would be that you have customized the td and th tags? If yes, please
> reset the customization, you need the new default values (which you then can
> still modify).
>
> Please check the variables org-export-table-header-tags and
> org-export-t
Hi Sebastian,
my guess would be that you have customized the td and th tags? If
yes, please reset the customization, you need the new default values
(which you then can still modify).
Please check the variables org-export-table-header-tags and
org-export-table-data-tags.
- Carsten
On Oct
Carsten Dominik writes:
>> | | | |
>> | A | B | C |
>> | 1 | 2 | 3 |
>> | 12 | 13 | 300 |
>> | 9 | 11 | 4 |
>
> I have now fixed this issue, at least for the HTML exporter.
>
> 1. The HTML exporter now puts a style attribute onto each
>individual field to make sure the fi
On Oct 20, 2010, at 7:16 PM, Bernt Hansen wrote:
Jeff Horn writes:
Is there a way to specify a particular column in org-mode that will
be
exported right-aligned in HTML?
| A | B | C |
| 1 | 2 | 3 |
For the table above, I would like column C right aligned when I
export
to HTML, but the
Sebastian Rose writes:
> Carsten Dominik writes:
>> On Oct 21, 2010, at 9:36 AM, Christian Moe wrote:
>>
>>> On 10/21/10 2:25 AM, Sebastian Rose wrote:
>>> (...)
>
> | | | |
> | A | B | C |
> | 1 | 2 | 3 |
> | 12 | 13 | 300 |
> | 9 | 11 | 4 |
>>>
Carsten Dominik writes:
> On Oct 21, 2010, at 9:36 AM, Christian Moe wrote:
>
>> On 10/21/10 2:25 AM, Sebastian Rose wrote:
>> (...)
| | | |
| A | B | C |
| 1 | 2 | 3 |
| 12 | 13 | 300 |
| 9 | 11 | 4 |
>>>
>>>
>>> I get
>>>
>>>
>>>
>>>
>>> as e
On Oct 21, 2010, at 9:36 AM, Christian Moe wrote:
On 10/21/10 2:25 AM, Sebastian Rose wrote:
(...)
| | | |
| A | B | C |
| 1 | 2 | 3 |
| 12 | 13 | 300 |
| 9 | 11 | 4 |
I get
align="right" />
as expected.
That's interesting. From the same example I get
align="ri
On 10/21/10 2:25 AM, Sebastian Rose wrote:
(...)
| | | |
| A | B | C |
| 1 | 2 | 3 |
| 12 | 13 | 300 |
| 9 | 11 | 4 |
I get
as expected.
That's interesting. From the same example I get
/>
...using freshly pulled 7.01trans. What might account for the difference?
Bernt Hansen writes:
> Jeff Horn writes:
>
>> Is there a way to specify a particular column in org-mode that will be
>> exported right-aligned in HTML?
>>
>> | A | B | C |
>> | 1 | 2 | 3 |
>>
>> For the table above, I would like column C right aligned when I export
>> to HTML, but the other colum
On Wed, Oct 20, 2010 at 3:04 PM, Christian Moe wrote:
> #+style: tr td + td + td {text-align: right;}
Thanks Christian, this workaround is OK for me at the moment since I'm
just making this change in one file.
+1 (naturally) for the exporter honoring column alignment settings.
--
Jeffrey Horn
On 10/20/10 7:16 PM, Bernt Hansen wrote:
Jeff Horn writes:
Is there a way to specify a particular column in org-mode that will be
exported right-aligned in HTML?
| A | B | C |
| 1 | 2 | 3 |
For the table above, I would like column C right aligned when I export
to HTML, but the other column a
Jeff Horn writes:
> Is there a way to specify a particular column in org-mode that will be
> exported right-aligned in HTML?
>
> | A | B | C |
> | 1 | 2 | 3 |
>
> For the table above, I would like column C right aligned when I export
> to HTML, but the other column aligned in the default way (lef
37 matches
Mail list logo
