Replies: 20 comments 30 replies
-
|
Since table.el tables are not easy to edit, maybe we can keep the org table format, but use tags to mark compound cell boundaries. By merging content of the sub cell,we get the compound cell content. For example: instead of Of course short tag is preferable, like We can even keep the tags and use a libreoffice plugin to do the merge after export. Maybe some ideas can be borrowed from ftable for text rebalancing in the region with tags |
Beta Was this translation helpful? Give feedback.
-
|
For fun sake I just exported to
with nothing but what is already there. You really can go very far with what is already there.. Typing out the list table wasn't fun, but the result was worth it. All the relevant details are here: AppendixThis is the unit test file ... |
Beta Was this translation helpful? Give feedback.
-
|
That is very impressive thanks for sharing, that will enter my documentation directory for sure!! |
Beta Was this translation helpful? Give feedback.
-
|
Another comment: I cannot see any difference between the two tables in the odt file (using Libreoffice 6.2), while of course I see the differences in the org file |
Beta Was this translation helpful? Give feedback.
-
|
I just did an experiment: I removed a being and end center from sales, and ups the table is distorted. That looks a bit counter intuitive, but I don't know the reason |
Beta Was this translation helpful? Give feedback.
-
Here is the fixed version. I have gitted the folder. So, you can run without-center-command-fixed.zip This is what the results look like
Two issues:
I have also made the "Region" string very big to highlight the inadequacy of list tables. Since the subtables are independent of each other, they have a mind of their own, and if the column sizes don't match, you get rules where you don't expect. Like what you see below. (Hint: There is no extra cell, so to speak. Intuitively you can sense what I mean here ...) Here is the diff diff --git a/complex-short.odt b/complex-short.odt
index afdf3a8..cfd1113 100644
Binary files a/complex-short.odt and b/complex-short.odt differ
diff --git a/complex-short.org b/complex-short.org
index 008abbf..604095b 100644
--- a/complex-short.org
+++ b/complex-short.org
@@ -107,80 +107,79 @@ Table above typeset with cell-borders.
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- | <1> | <l10> |
--
- - Region
- -
+-
+ - Region ................................................................
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- -
- -
+ -
+ -
Sales
-
- -
- -
+ -
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- | <c> | <c> |
- -
- -
+ -
+ -
#+begin_center
Q1
#+end_center
- -
+ -
#+begin_center
Q2
#+end_center
- -
+ -
#+begin_center
Q3
#+end_center
- -
+ -
#+begin_center
Q4
#+end_center
- -
- -
+ -
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- -
- -
+ -
+ -
foo
- -
+ -
bar
- -
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- -
- -
+ -
+ -
foo
- -
+ -
bar
- -
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- -
- -
+ -
+ -
foo
- -
+ -
bar
- -
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- -
- -
+ -
+ -
foo
- -
+ -
bar
--
+-
- North
- -
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- -
+ -
- 350
- 46
- 253
@@ -189,12 +188,12 @@ Table above typeset with cell-borders.
- 42
- 382
- 68
--
+-
- South
- -
+ -
#+ATTR_ODT: :style "GriddedTableNew"
#+ATTR_ODT: :list-table t
- -
+ -
- 462
- 84
- 511
|
Beta Was this translation helpful? Give feedback.
-
|
excellent, thanks for clarifying. I, now, even managed to get rid of all centered cells, I really think both approaches are needed
here is my org file without centered cells/tables (using the latest commit, I just byte compiled it and removed the pkg |
Beta Was this translation helpful? Give feedback.
-
|
(on mobile)
You need to execute the src block you see at the beginning of the file
which defines the new gridded table style and associates it with custom
new automatic styles.
The automatic styles remove the padding around tables. So the tables
overlap. If you watch closely rules will be thicker where the tables
overlap. But it is nearly perceptible in the screenshot I started
…On Sun, 3 Oct, 2021, 22:24 Uwe Brauer, ***@***.***> wrote:
Another comment: I cannot see any difference between the two tables in the
odt file (using Libreoffice 6.2), while of course I see the differences in
the org file
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#102 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXTBKHD23TH6SKSKKYTZQDUFCDF7ANCNFSM5FGGRXDQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Ah, of course, this really is then a much better solution!! I like it very much |
Beta Was this translation helpful? Give feedback.
-
|
(contd)
IIf you observe closely rules will be thicker where the tables overlap. But
it is barely perceptible in the screenshot I shared. I am not sure if the
difference in the thickness will be perceptible in print.
…On Sun, 3 Oct, 2021, 22:24 Uwe Brauer, ***@***.***> wrote:
Another comment: I cannot see any difference between the two tables in the
odt file (using Libreoffice 6.2), while of course I see the differences in
the org file
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#102 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXTBKHD23TH6SKSKKYTZQDUFCDF7ANCNFSM5FGGRXDQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Impressive it may seem ... but it is all a sleight of hand. To understand
the inadequacy of the solution make the "Region" string in first table cell
very big like "Region ....." .
…On Sun, 3 Oct, 2021, 17:47 Uwe Brauer, ***@***.***> wrote:
That is very impressive thanks for sharing, that will enter my
documentation directory for sure!!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#102 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXTBKCIE3HWMA7F64QS6Z3UFBCV3ANCNFSM5FGGRXDQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
I checked, I wrote The region is very very big, it then gets a line break, but this was to be expected. I am not sure I understand the problem? |
Beta Was this translation helpful? Give feedback.
-
|
It's impressive. Nesting list tables makes it hard to see the table structure within the list table. I would rather use libreoffice to do the editing and include the odt file in the org file. |
Beta Was this translation helpful? Give feedback.
-
|
Right, it is a bit like using latex for generating the able, compiling and viewsing a pdf file, but it has the huge benefit of using emacs for your editing which I always prefer over editing with libreoffice. BTW I am not sure I understand what you mean by saying include the odt in the org file. |
Beta Was this translation helpful? Give feedback.
-
|
I doubt you would like to edit that example table in emacs, you are asking for trouble :-). I am joking. BTW, there is a feature called transclusion of of ODT document: |
Beta Was this translation helpful? Give feedback.
-
|
>> "Q" == QiangF ***@***.***> writes:
I doubt you would like to edit that example table in emacs, you are
asking for trouble :-). I am joking. BTW, there is a feature called
transclusion of of ODT document:
#+ATTR_ODT: :transclude t
[[file:complicated_table.odt]]
That is interesting. So you can use that command and then export the org file, again, to odt?
|
Beta Was this translation helpful? Give feedback.
-
|
It's a surrender to reality, by using [[file:complicated_table.odt]]. I prefer a concise table in org mode format, but list table is too loose for that purpose. :-) |
Beta Was this translation helpful? Give feedback.
-
|
I have added support for row and colspans. See #104. This is an EXPERIMENTAL feature. I am open to suggestions on what the |
Beta Was this translation helpful? Give feedback.
-
|
thanks! |
Beta Was this translation helpful? Give feedback.
-
|
You can download the updated whole package here https://github.com/kjambunathan/kjambunathan.github.io/blob/a4aa0ba670596343ef50e99ef38c5dad43e7df40/elpa/ox-odt-9.3.7.327.tar |
Beta Was this translation helpful? Give feedback.
-
|
A problem with tables that does not fit on one page, they do not break |
Beta Was this translation helpful? Give feedback.
-
You have found practical use for this function ... Why not ask the author to convert the gist in to a proper MELPA package. For my own later reference ... See
(defun randomise-region ()
"Like `ap/replace-words-randomly', but only replace inside region if it is
active.
If the region is not active, replace from point to the end of the
buffer. The region is never considered active outside
`transient-mark-mode'. "
(interactive)
(if (or (and (boundp 'zmacs-region-active-p) zmacs-region-active-p)
(and (boundp 'transient-mark-mode) transient-mark-mode mark-active))
(save-restriction
(save-excursion
(narrow-to-region (point) (mark))
(goto-char (point-min))
(ap/replace-words-randomly)))
(ap/replace-words-randomly)))From Emacs: Replace all words in buffer with random words of the same length ;; This function replaces all words in a buffer with words of the same length,
;; chosen at random from /usr/share/dict/words. Words are replaced consistently,
;; so e.g. "A" is always replaced with "Z". The mapping changes when Emacs is
;; restarted or when the cache buffer is killed. If all unique words of a certain
;; length are exhausted, random strings are used.
(defun ap/replace-words-randomly (&optional buffer)
"Replace all words in BUFFER or current buffer with randomly selected words from the dictionary.
Every time a new word is found, it is mapped to a replacement
word, so every instance of word A will be replaced with word Z."
(interactive)
(require 'ht)
(with-current-buffer (or buffer (current-buffer))
(let ((replacements (ht-create))
(used-words (ht-create))
(regexp (rx (or bow symbol-start) (1+ word) (or eow symbol-end)))
(case-fold-search t)
(orig-mode major-mode)
;; (window (get-buffer-window (current-buffer)))
(buffer-size (buffer-size))
current-word replacement-word)
(fundamental-mode)
(goto-char (point-min))
(while (re-search-forward regexp nil 'noerror)
(setq current-word (s-downcase (match-string 0)))
(save-match-data ; `ap/get-random-word-of-same-length' changes match data
(unless (setq replacement-word (ht-get replacements current-word))
;; Find unique replacement word and add to hash-tables.
;; We use a second ht to store words that we've already
;; used, because looking them up as keys is much faster
;; than getting all the values in the replacements table.
(while (ht-get used-words
(setq replacement-word (ap/get-random-word-of-same-length current-word used-words)))
nil)
(unless replacement-word
;; No word found; make random string (which may not be
;; unique, but we can't really guarantee uniqueness in the
;; case of very short words unless we go into non-word
;; characters, Unicode, etc)
(setq replacement-word (ap/get-random-string (length current-word))))
;; TODO: Filter profanity?
;; Add to hash-tables
(ht-set replacements current-word replacement-word)
(ht-set used-words replacement-word t)))
;; Replace match
(replace-match replacement-word nil 'literal)
;; Allow Emacs to be interrupted gracefully. Also potentially
;; displays progress if you have the buffer visible, but I can't get
;; recentering to work.
(sit-for 0)
;; Display progress (this takes a while on large buffers)
(message "%s/%s" (point) buffer-size)
;; No idea why this doesn't work. I have to save and restore
;; point manually or it doesn't move past the matches and runs
;; in an infinite loop, but then recenter does nothing at all
;; (when window
;; (setq save-point (point))
;; (with-selected-window window
;; (recenter t))
;; (goto-char save-point))
)
(funcall orig-mode))))
(cl-defmacro ap/with-random-word-cache (&rest body)
""
(declare (indent defun)
(debug (&rest form)))
(let ((result (cl-gensym)))
`(progn
(unless (and (boundp 'ap/random-word-buffer)
(buffer-live-p ap/random-word-buffer))
(with-current-buffer (setq ap/random-word-buffer (get-buffer-create " *RANDOM WORDS*"))
(call-process-shell-command "cat /usr/share/dict/words | shuf" nil t))
(setq ap/random-word-buffer-point 1))
(with-current-buffer ap/random-word-buffer
(let (,result)
(goto-char ap/random-word-buffer-point)
(setq ,result (progn ,@body))
;; This point-saving and restoring should NOT be necessary, I have no idea why this is.
(setq ap/random-word-buffer-point (point))
,result)))))
(defun ap/get-random-word-of-same-length (word &optional exclude-ht)
(let* ((length (length word))
(regexp (rx-to-string `(seq bol (repeat ,length word) eow))))
(ap/with-random-word-cache
;; Search from last point, wrap once
(when (= (point) (point-max))
(goto-char (point-min)))
(cl-loop with starting-point = (point)
with match
with wrapped
until (or match
(and wrapped
(>= (point) starting-point)))
do (progn
(when (= (point) (point-max))
(goto-char (point-min))
(setq wrapped t))
(when (re-search-forward regexp nil 'goto-end)
(setq match (match-string 0))
(unless (and (not (string= match word))
(or (not exclude-ht)
(not (ht-get exclude-ht match))))
;; Invalid match, clear var
(setq match nil))))
finally return match))))
(defun ap/get-random-string (length)
"Return random string of LENGTH."
(unless (and (bound-and-true-p ap/random-chars)
(bound-and-true-p ap/random-chars-length))
(setq ap/random-chars (split-string "abcdefghijklmnopqrstuvwxyz" "" t))
(setq ap/random-chars-length (length ap/random-chars)))
(let* (s)
(while (< (length s) length)
(setq s (concat s (nth (random ap/random-chars-length) ap/random-chars))))
s))
|
Beta Was this translation helpful? Give feedback.
-
|
Concerning of writing the author, this was my first thought, but in his gist repository, I did not find any address, I will look again, BTW on emacs help another user provided a similar functionality, however his approach randomise all words (that is the replacement is not done necessarily by words of the same length, making it not that practical for my purpose because then the corresponding file might result in a different odt table |
Beta Was this translation helpful? Give feedback.
-
Url gives the author https://gist.github.com/alphapapa/2d141b60ccbe92f1b90000debde2ddd2. AP => Adam Porter on emacs-orgmode list and github-alphapapa on reddit. Btw, he should replace the numbers in the buffer too not just the words ... |
Beta Was this translation helpful? Give feedback.
-
|
Thanks I found his email address and wrote him |
Beta Was this translation helpful? Give feedback.
-
I just add to modify that table adding more stuff and it does not break again, I don't want to bother, also I think the table is already at its limit, concerning font size. line spacing etc. |
Beta Was this translation helpful? Give feedback.
-
|
I have updated the answer with
Apopos the above line .... That table is the largest row the table. So, I have "split" the table there. Forunately, the page break "naturally" appeared at that page. If not, I would have "enabed" the pagebreak line, Anyways, I realized there is a need for adding pagebreak before tables ... Currently pagebreak is supported only for paragraphs, and headlines. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks very much for this, I really appreciate it. (you seem to have telephatic skills read my thoughts on asking how to set the default language :) I have taken this as part of Bug: ODT exporter does not honour +LANGUAGE line [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)] |
Beta Was this translation helpful? Give feedback.
-
|
Instead of a monolithic top level table (of say 10 rows), create 10 takes
for 1 row beginning at a new page.
So, generate a monolithic take and see where the layout naturally breaks,
and then you explicitly put page breaks at those point.
Now this braking of monolithic table can happen at the top level or at
nested table.
It is difficult to describe these things by words, that is why I stare
screenshot or pdf files.
In the example I shared, the monolithic table is broken into two tables, so
first two rows become one table and the 3rd and 4 th table become the
second table.
I believe the pdf table I shared looks ok with you. (Your description alone
was NOT sufficient, I had to go a step further and interpret what you could
have meant)
If the pdf is not what you want, send me screenshots markup portions that
are NOT satisfactory to you. I will try my best to help you in your
endeavour.
If the 10 or 10.5 pt is too small or spacing is too small I can (trt to)
fix them. You are doing some real life submission and I would STRONGLY
suggest that you print it out and satisfy yourself that it looks good on
paper.
Let me reiterate, 1 picture is equivalent to 1000 words
I will fix the pagebreak bug for you. Intuitively I am convinced that it is
NOT A SHOWSTOPPER for what you want to achieve in your real life.
Tell me what the language is. Is it German or Deutch?
I wish you success in whatever you are doing and more than happy to help you
…On Thu, 7 Oct, 2021, 22:16 Uwe Brauer, ***@***.***> wrote:
A problem with tables that does not fit on one page, they do not break
To ensure that table fits snug on a page, there are lots of tools
available to you. One of it is the font size. The others are
1. Table column width (You can see that I have changed the relative
size of columns)
2. Line spacing -- single, double, 1.5 etc
3. Margins and padding on almost everything right from page styles
down to table cells and the paragraphs.
I just add to modify that table adding more stuff and it does not break
again, I don't want to bother, also I think the table is already at its
limit, concerning font size. line spacing etc.
while non nested tables that are generated by you exporter do break
automatically, it seem that this no longer holds for this nested tables, so
I have to break them my self, right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#102 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXTBKFK2K4QQPCTYVJYQNLUFXFHNANCNFSM5FGGRXDQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
I am on mobile so some words are spelled wrong. For example, table has
come out mistakenly as 'take' etc. Sorry about that
Send me a screenshot and Mark them up with gimp, paint or inkscape so that
I know what areas are bothering you and I can focus on addressing those.
That said,
(I feel) there is a LibreOffice bug in how it layouts table s. Once I
confirm my intuition, document foundation will get a big report (and you a
courtesy copy) in another few days.
…On Thu, 7 Oct, 2021, 22:37 Jambunathan K, ***@***.***> wrote:
Instead of a monolithic top level table (of say 10 rows), create 10 takes
for 1 row beginning at a new page.
So, generate a monolithic take and see where the layout naturally breaks,
and then you explicitly put page breaks at those point.
Now this braking of monolithic table can happen at the top level or at
nested table.
It is difficult to describe these things by words, that is why I stare
screenshot or pdf files.
In the example I shared, the monolithic table is broken into two tables,
so first two rows become one table and the 3rd and 4 th table become the
second table.
I believe the pdf table I shared looks ok with you. (Your description
alone was NOT sufficient, I had to go a step further and interpret what you
could have meant)
If the pdf is not what you want, send me screenshots markup portions that
are NOT satisfactory to you. I will try my best to help you in your
endeavour.
If the 10 or 10.5 pt is too small or spacing is too small I can (trt to)
fix them. You are doing some real life submission and I would STRONGLY
suggest that you print it out and satisfy yourself that it looks good on
paper.
Let me reiterate, 1 picture is equivalent to 1000 words
I will fix the pagebreak bug for you. Intuitively I am convinced that it
is NOT A SHOWSTOPPER for what you want to achieve in your real life.
Tell me what the language is. Is it German or Douch?
I wish you success in whatever you are doing and more than happy to help
you
On Thu, 7 Oct, 2021, 22:16 Uwe Brauer, ***@***.***> wrote:
> A problem with tables that does not fit on one page, they do not break
>
> To ensure that table fits snug on a page, there are lots of tools
> available to you. One of it is the font size. The others are
>
> 1. Table column width (You can see that I have changed the relative
> size of columns)
> 2. Line spacing -- single, double, 1.5 etc
> 3. Margins and padding on almost everything right from page styles
> down to table cells and the paragraphs.
>
> I just add to modify that table adding more stuff and it does not break
> again, I don't want to bother, also I think the table is already at its
> limit, concerning font size. line spacing etc.
> while non nested tables that are generated by you exporter do break
> automatically, it seem that this no longer holds for this nested tables, so
> I have to break them my self, right?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#102 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEXTBKFK2K4QQPCTYVJYQNLUFXFHNANCNFSM5FGGRXDQ>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
|
Beta Was this translation helpful? Give feedback.
-
|
My example doesn't modify any "nestingness". The "nestingness' is exactly
same as what you shared with me. This is deliberate ..... Without
understanding what is in those little boxes I really don't know how they
should be grouped. I assumed you already had them in a way that reflected
what was in the "scanned" pdf form handed out to you.
I have ONLY changed the font size, column widths and "broke' the table in to two at
exactly where the (commented out) page break appears. First 2 rows form the
first table. The 3rd and 4 th row becomes the second table. The 3rd row
is really big so it spans more than one page. (There is NO way you can
put it in a single page BUT you can have the header portions carried over
to next page by introducing hlines) What you want depends on what those
boxes mean ... and the semantics are opaque to me. So any interpretation
or a judgement call on my part is no different from shooting with both my
eyes shut and hoping that it hits the target.
…On Thu, 7 Oct, 2021, 22:16 Uwe Brauer, ***@***.***> wrote:
A problem with tables that does not fit on one page, they do not break
To ensure that table fits snug on a page, there are lots of tools
available to you. One of it is the font size. The others are
1. Table column width (You can see that I have changed the relative
size of columns)
2. Line spacing -- single, double, 1.5 etc
3. Margins and padding on almost everything right from page styles
down to table cells and the paragraphs.
I just add to modify that table adding more stuff and it does not break
again, I don't want to bother, also I think the table is already at its
limit, concerning font size. line spacing etc.
while non nested tables that are generated by you exporter do break
automatically, it seem that this no longer holds for this nested tables, so
I have to break them my self, right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#102 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXTBKFK2K4QQPCTYVJYQNLUFXFHNANCNFSM5FGGRXDQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
ok, I see, that I confused myself a bit, I think i will finish the document first, and see how the break work, because right now it seems to work, sorry for the noise but it seems easily possible to be confused in which column to put the |
Beta Was this translation helpful? Give feedback.
-
|
Hi |
Beta Was this translation helpful? Give feedback.
-
How are you exporting from LibreOffice -- command line or through UI? What is the specific version of Microsoft Word you are using? What is the MS Word format that you are using? There are plenty of Microsoft Word formats around.
A cursory google search suggests that nested tables are common in Microsoft land. See https://www.google.com/search?client=firefox-b-e&q=%22nested+table%22+%22microsoft+word%22+site%3Ayoutube.com Try your luck in https://ask.libreoffice.org/. It is "not" just a user forum. Some of the people who respond there "sound" like developers/architects. If not that, they surely are very technically-minded old hands. If you think you have exhausted your options, you need to file a bug report with https://bugs.documentfoundation.org/. (I think) if you mention that a ODT file created by LibreOffice gets garbled when exported to docx, I am sure you will get good leads or help. Compatibility issues take high priority. If you sneak in the word "Compatibility" then it will attract right set of eyes and attention ... |
Beta Was this translation helpful? Give feedback.
-
I resorted to using nested tables, because when this discussion started there was no support for row and colspan in tables. Now that there is support for spanned cells, there is really no need for nested tables at all. A simple plaint list -able will do. As I write this, I have already reworked your long scrambled table so that it is totally NOT NESTED and very SIMPLE list-table. In the process of re-working, I realized that you may need better control of relative column sizes. So, I have opened this issue Add support for relative column widths in tables with spanned cells · Issue #107. Btw, I will share the table code, once I have addressed all the issues that concern the typesetting of the long scrambled tabe .... |
Beta Was this translation helpful? Give feedback.
-
|
Surely there are nested tables in Microsoft Word https://www.howtogeek.com/howto/microsoft-office/nesting-a-table-inside-a-table-in-word-2007/. |
Beta Was this translation helpful? Give feedback.
-
|
>> "JK" == Jambunathan K ***@***.***> writes:
> LO can deal well with them, however I had to export that to docx (that format, sadly, is more common) using LO's converter.
How are you exporting from LibreOffice -- command line or through UI?
In principle both, but the very last version of the odt document by the UI.
What is the specific version of Microsoft Word you are using?
My collaborator has a bit old version 2011, he told me, I have also access to MS Word 2020/21 but since I am not really acquainted with it, I did not risk to try to edit table with it
What is the MS Word format that you are using? There are plenty of Microsoft Word formats around.
Docx. It seems that doc was a bit better for that old MS Word version
https://blog.desdelinux.net/en/optimiza-libreoffice-para-que-tenga-mejor-compatibilidad-con-microsoft-office/
> Then I learnt that MS Word does not support nested tables.
A cursory google search suggests that nested tables are common in
Microsoft land. See
https://www.google.com/search?client=firefox-b-e&q=%22nested+table%22+%22microsoft+word%22+site%3Ayoutube.com
Hm, according to
https://publica.fraunhofer.de/eprints/urn_nbn_de_0011-n-1047639.pdf
they are not, not sure how recent that document is.
-----
Try your luck in https://ask.libreoffice.org/. It is "not" just a user
forum. Some of the people who respond there, seem to be developers and
are very technically-minded old hands.
If you think you have exhausted your options, you need to file a bug
report with https://bugs.documentfoundation.org/. (I think) if you
mention that a ODT file created by LibreOffice gets garbled when
exported to docx, I am sure you will get good leads or help.
Compatibility issues take high priority.
Thanks, but if, as you said in another email, nested tables can be avoided, then I prefer to stick with plain tables, just in case
|
Beta Was this translation helpful? Give feedback.
-
See this zip file too-long-table-fixed-v2.zip. The ODT file in there does NOT use any nested tables. It is just 3 tables, specifically 3 list-tables one after the other. This is bird's eye view of how the table looks like in Emacs buffer .... As you can see, it uses all the below features that came up as part of this discussion
|
Beta Was this translation helpful? Give feedback.
-
|
My suggestion was to add this (load-file "/home/kjambunathan/src/org-mode-ox-odt-master/lisp/ox-odt.el")or (load-file "/home/kjambunathan/.emacs.d/elpa/ox-odt-9.3.7.331/ox-odt.el")in your .emacs right at the very last line. Problem solved. It will work with new or old versions of org.
It is based on 9.3.7. The prefix of the package tar file says the base version. What you see in the file is is the minimal version of org expected.
It will definitely happen. This is the status as on May 2021 https://github.com/kjambunathan/org-mode-ox-odt/commits/citeproc-wip. I got busy after May 2021. As I said, simply load the file as the last step in your .emacs, and it will/should work. |
Beta Was this translation helpful? Give feedback.
-
|
(Courtesy link for some one who stumbles on to this discussion) I have added support for |
Beta Was this translation helpful? Give feedback.
-
|
I wish there were a more simple way to add the left hand rule to the table. The standard org syntax doesn't seem to parse. |
Beta Was this translation helpful? Give feedback.
-
I am not sure what you are trying to do there. If you are looking for ready to use snippets then consult List of features that are exclusive to The Enhanced OpenDocument Exporter for Org mode The example table in Now size table columns using `:widths’ attribute works fine for me. It has both horizontal and vertical rules. |
Beta Was this translation helpful? Give feedback.
-
|
I would like to have a table with gridlines on all sides. My quote shows how you indicate that for latex export. |
Beta Was this translation helpful? Give feedback.
-
|
Also @kjambunathan, how do you get to work? |
Beta Was this translation helpful? Give feedback.
-
What you pasted works for me. The `Heading' appears on a new page. What are you expecting. Ensure that you are using my version of ODT exporter, and not the one that comes with Doom Emacs. Export a file, and look at the |
Beta Was this translation helpful? Give feedback.
-
|
OK I managed to get it working in a minimal case... something is blocking it in my larger file that I need to go debug. Is this option listed in the manual? |
Beta Was this translation helpful? Give feedback.
-
There is no formal manual, apart from the link I shared earlier SNIPPETS The snippets there are simple and if you export them and see the ODT output you can reasonably guess what the snippet is doing. If you want a gridded table see the |
Beta Was this translation helpful? Give feedback.
-
Hi
it is my understanding that org still does not support merged cells in tables
see for example
https://lists.gnu.org/archive/html/emacs-orgmode/2010-08/msg00882.html
although this is 11 years old, it seems that it still is not supported, however some proposals are done in this thread and a recommendation to use table.el
however the org-mode-ox-odt exporter supports using list to convert them to tables, so the question is, could
that include or produce merged cells as in
Beta Was this translation helpful? Give feedback.
All reactions