From: Uwe Brauer <oub@mat.ucm.es>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: RLT (hebrew) tables and org-odt-export-to-odt problems
Date: Mon, 04 Nov 2013 23:54:19 +0100 [thread overview]
Message-ID: <87a9hjrd5w.fsf@mat.ucm.es> (raw)
In-Reply-To: 87ob60pum7.fsf@gmail.com
[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]
>> "Jambunathan" == Jambunathan K <Jambunathan> writes:
Hi Jambunathan,
> Uwe
> I am venturing in to the wild here and it will take multiple iterations
> for me to even get a "feel" for what needs to be happen. I am not even
> sure what is right or wrong here. Anyways...
> ----------------------------------------------------------------
thanks very much for all your efforts so far.
> Further to our exchange on the emacs-devel list,
> http://lists.gnu.org/archive/html/emacs-devel/2013-11/msg00134.html
> I see that the file you passed me has no bi-directional markers
> whatsoever. I think presence of markers would affect how libreoffice
> would layout the table.
> I suggest that you pass me an Org file, that has the right
> bidi-paragraph-direction (as a local variable) and has the right set of
> bidi markers.
I tried and that and it did not help I send the files anyway, I will
however use thunderbird to send the attachments in the next mails.
> (Furthermore, explicitly mark the org file as utf-8 coded. I am not
> sure what coding system the attachment is coded to. When I view the
> attachment in Gnus, I only see the latin characters.)
> ----------------------------------------------------------------
> As for getting the table cells laid right, try this out.
> 1. Export a hebrew.org file to hebrew.odt
> 2. Open the .odt file in LibreOffice.
F11-> Page Style->Default Page Style->Page->Text Direction->Set it to
> "Right to Left".
This does not really work, since it switches the direction of all rows
in the table, but not just of the first one as suggested Eli.
> I think that this would set the predominant direction of your
> document. I believe, it would correspond to bidi-paragraph-direction
> setting.
> 3. File->Save as->somefile.ott
> Now in your hebrew.org file, add this directive
> #+ODT_STYLES_FILE: "hebrew.ott"
> This will make the exported document an R2L document.
> 4. Export again. See what happens
I tried same result.
I send all files in question in my next email.
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5556 bytes --]
next prev parent reply other threads:[~2013-11-04 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 13:33 RLT (hebrew) tables and org-odt-export-to-odt problems Uwe Brauer
2013-10-30 20:41 ` Jambunathan K
2013-10-30 23:17 ` Uwe Brauer
2013-10-30 23:27 ` NOT SOLVED " Uwe Brauer
2013-10-30 23:37 ` org-odt-export-to-odt, tables bug in OO Uwe Brauer
2013-10-31 10:41 ` RLT (hebrew) tables and org-odt-export-to-odt problems Uwe Brauer
2013-11-04 6:08 ` Jambunathan K
2013-11-04 22:54 ` Uwe Brauer [this message]
2013-11-04 22:57 ` Uwe Brauer
2013-11-06 14:51 ` Uwe Brauer
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=87a9hjrd5w.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).