Provide some keywords to set ODT metadata.

[hwiorn]

Currently, exporter doesn't make general and custom properties of an ODT file. I can't set any general fields and add any custom fields inside an ODT document using ox-org only. I can define user custom fields in #+ODT_MASTER_STYLES, But I can't set them to metadata.

I checked ox-odt.el, and I found it checks only some keywords like title, author, description, etc.

I think that ox-odt needs to provide a custom property which can be overridden or #+ODT_EXTRA_META is a suitable solution.

#+property: created <2021-10-26 Tue>
#+property: modified <2021-10-27 Wed>

or

#+ODT_GENERAL_META: modified <2021-10-26 Tue>
#+ODT_CUSTOM_META: Version 1.1.1
#+ODT_CUSTOM_META: Document-Id A-21-10-25-REQ-11

or

#+ODT_EXTRA_META: <dc:date>2021-10-27T17:18:01.220502029</dc:date><meta:editing-duration>PT6M31S</meta:editing-duration><meta:editing-cycles>6</meta:editing-cycles><meta:generator>LibreOffice/7.2.2.2$Linux_X86_64 LibreOffice_project/20$Build-2</meta:generator>

[kjambunathan]

You can already export properties with prop:t option. Look at an the Org snippet / screenshot example this issue: #95.

Can you give me more idea on your specific situation ....

1. What sort of user fields you want to put in meta.xml?
2. Where do you intend to use those fields? In document header / footer or inline within the document

I don't use properties or keywords much and at this point in time I have no clarity on what woud be the most flexible way to specify user fields ... keywords or properties? If you have specific suggestions I will consider them.

In principle I will take up your request for additional user fields .....

[hwiorn]

I'm trying to rewrite my model evaluation test results and technical support manuals to org file with ODT templates.
I found my issue is referencing variables(user field) in header and footer.
I couldn't use the macro-replacement feature in +CUSTOM_EXTRA_STYLE so I used user-fields which can be controlled by custom properties in a document.

The one of my documents consists custom cover page which has no header and footer and other pages which is the general company document form which has speicific document information.
I have to set title:nil author:nil. It means I need to define title alternative custom property for header.

The form of a header

| IMG  |                                        <TITLE>                                                   | <Company |
| LOGO | Doc-Id | <DocID> | Version |  <DocVersion> | Created | <CreatedDate> | Modified | <ModifiedDate> | Name>    |

The form of a footer

| <CurrentDate> |                   <PageNumber> / <PageCount>                          |  <CompanyName> <Department> |

[kjambunathan]

Provide some keywords to set ODT metadata

I have added this feature. See #117 for more details.

The form of a header

| IMG  |                                        <TITLE>                                                   | <Company |
| LOGO | Doc-Id | <DocID> | Version |  <DocVersion> | Created | <CreatedDate> | Modified | <ModifiedDate> | Name>    |

If the document is in English, then the header will be too cramped. If you are using korean or other east-asian languages this may not be the case.

Here is a zip file for you to experiment with
docproperties.zip

Note that I have used "transcluded table" (instead of list table). Regarding alignment, I am not sure if you are talking about horizontal alignment or vertical alignment. Horizontal alignment doesn't work right now in list tables or transcluded tables, because of #25. I will remove handicap in next few days. If you are talking about vertical alignment in tables, look at #110 (comment).

I am not done with this discussion. Experiment, and let me know what you think or want.

To get this,

do this,

#+odt_preferred_output_format: pdf

#+begin_src emacs-lisp :exports results :results silent
(add-to-list 'org-odt-experimental-features 'transclude-sole-footnote-references-in-a-table)
#+end_src

#+ODT_DOCUMENT_PROPERTIES: DOC-TITLE DOC-COMPANY-NAME DOC-ID DOC-VERSION DOC-CREATED-DATE DOC-MODIFIED-DATE

#+DOC-TITLE:            Custom fields
#+DOC-COMPANY-NAME:     Org Mode ODT Exporter
#+DOC-ID:               ox-odt-8d6d991d-df0c-4aec-a548-ada78dd554ee
#+DOC-VERSION:          1.0
#+DOC-CREATED-DATE:     [2021-10-19 Tue]
#+DOC-MODIFIED-DATE:    <2021-10-29 Fri>

#+MACRO: DocTitle {{{keyword-to-documentproperty(DOC-TITLE)}}}
#+MACRO: CompanyName {{{keyword-to-documentproperty(DOC-COMPANY-NAME)}}}
#+MACRO: DocID {{{keyword-to-documentproperty(DOC-ID)}}}
#+MACRO: DocVersion {{{keyword-to-documentproperty(DOC-VERSION)}}}
#+MACRO: CreatedDate {{{keyword-to-documentproperty(DOC-CREATED-DATE)}}}
#+MACRO: ModifiedDate {{{keyword-to-documentproperty(DOC-MODIFIED-DATE)}}}

Nunc eleifend leo vitae magna.  Nunc eleifend leo vitae magna.
Curabitur lacinia pulvinar nibh.  Donec posuere augue in quam.
Aliquam posuere.  Nullam rutrum.  Aliquam posuere.

#+ATTR_ODT: :style "GriddedTable"
#+ATTR_ODT: :rel-width 100
#+ATTR_ODT: :widths "15, 8 , 8 , 8 , 8 , 8 , 8 , 8 , 8 , 8"
#+ATTR_ODT: :span "@1$1{3:1} @1$2{1:4} @1$6{3:1}"
| <l2>   |        <r1> | <1>              | <1>               | <1>                | <1>               |
| [fn:1] |      [fn:2] |                  |                   |                    | {{{CompanyName}}} |
|        |      Doc-Id | Version          | Created           | Modified           |                   |
|        | {{{DocID}}} | {{{DocVersion}}} | {{{CreatedDate}}} | {{{ModifiedDate}}} |                   |
[fn:1]

#+ATTR_ODT: :inner-frame (anchor "as-char")
#+ATTR_ODT: :width 2
[[./org-mode-unicorn.png]]

[fn:2]

#+begin_center
{{{DocTitle}}}
#+end_center

[hwiorn]

I have added this feature. See #117 for more details.

Thank you for your fast patch! I'm checking out it now.
And how about general properties?
I think it has benefits for indexing like file search engine, spotlight to share documents to other people.

If the document is in English, then the header will be too cramped. If you are using korean or other east-asian languages this may not be the case.

I'm making two version(english, korean) of the template now. I think it's not matter because the header font size is so small(8pt).

Note that I have used "transcluded table" (instead of list table).

I didn't know transcluded table. Is it a new feature of enhanced ox-odt? I can't find any reference of it.

And could you make a value type in custom fields?

org-mode-ox-odt/lisp/ox-odt.el

Lines 2506 to 2516 in e90550e

	(defun org-odt--define-custom-field (key value)
	"Install a user-define variable NAME with value VALUE in meta.xml.
	See entry titled `keyword-to-documentproperty' in
	`org-odt-global-macros' for more information."
	(when (org-string-nw-p key)
	(let ((value-type "string"))
	(format "\n<meta:user-defined meta:value-type=\"%s\" meta:name=\"%s\" >%s</meta:user-defined>\n"
	value-type
	(org-odt--encode-plain-text key)
	(org-odt--encode-plain-text (or value ""))))))

You hard-coded string type in custom field. I think it's better if there is specific value-type like #+DOC-CREATED-DATE: [2021-10-19 Tue] :type date. Because ODT doesn't understand date type of org and always represents as string type.

[kjambunathan]

I didn't know transcluded table. Is it a new feature of enhanced ox-odt? I can't find any reference of it.

Always search for what you are looking for in either the issues or code. See Add support for "Transcluded Tables"

And how about general properties?
I think it has benefits for indexing like file search engine, spotlight to share documents to other people.

Could you tell me specific examples what you mean by general properties? I need to see what fields are of interest to you, so that I can find out all that needs to be done to help you produce the document you are working on.

You hard-coded string type in custom field. I think it's better if there is specific value-type like keyword-to-documentproperty-with-type(DOC-CREATED-DATE, date). Because ODT doesn't understand date type of org and always represents as string type.

I was anticipating this request ... There is already good amount of code to deal with date fields, in timestamp ... including how the value may be displayed.

But I had to apply brakes because of a bug somewhere, and I couldn't get it to work. (If you could help me with isolating the issue, I will be happy. It will make things faster for you and easier for me.)

These are good starting points

See

org-mode-ox-odt/lisp/ox-odt.el

Line 159 in e90550e

(:odt-use-date-fields nil nil org-odt-use-date-fields)

org-mode-ox-odt/lisp/ox-odt.el

Line 2417 in e90550e

(defun org-odt--build-date-styles (fmt style)

The bug is probably because of code-rot, i.e., the code might have diverged in the last decade or so and I think it is because Emacs Date Time APIs have changed and ox.el or org.el haven't quite caught up with it. There is no other exporter that handles date / datetime types like the ODT exporter does. I think the issue is somewhere here (or the manner in which I or ox.el invoke it)

org-mode-ox-odt/lisp/org.el

Line 20120 in e90550e

(defun org-timestamp-format (timestamp format &optional end utc)

org-mode-ox-odt/lisp/org.el

Line 20105 in e90550e

(defun org-timestamp-to-time (timestamp &optional end)

As I requested, if you can debug a bit and help me with the root cause (or suggest a solution) I will appreciate it. I am not comfortable reviewing others code, so a simple text description will suffice ... don't bother about a PR. Whatever you choose to do, I will add support for value types in another week.

[hwiorn]

Always search for what you are looking for in either the issues or code.

I searched it in Issues and Google and I didn't find it. Maybe it was typo, I think.

Could you tell me specific examples what you mean by general properties? I need to see what fields are of interest to you, so that I can find out all that needs to be done to help you produce the document you are working on.

General properties is below image I already posted it. Sorry, I don't know what the correct term is.

They are already defined in ODT specification

• Created: <meta:creation-date>2021-10-01T10:12:34.823961119</meta:creation-date>
• Modified: <dc:date>2021-11-01T10:12:34.823961119</dc:date>
• Last printed: <meta:print-date>2021-10-01T10:12:34.823961119</meta:print-date>
• Revision number: <meta:editing-cycles>1</<meta:editing-cycles>
• Generator: <meta:generator>Org 9.5-??-888aaa9 enhanced-ox-odt 803ae54 </meta:generator>

But I had to apply brakes because of a bug somewhere, and I couldn't get it to work. (If you could help me with isolating the issue, I will be happy. It will make things faster for you and easier for me.)

I will check it :)

[kjambunathan]

Regarding date / datetime type fields, I wonder what format you want the date value to be displayed. Do korean users use different values of date or write them differently. This is what I mean.

[hwiorn]

Regarding date / datetime type fields, I wonder what format you want the date value to be displayed. Do korean users use different values of date or write them differently. This is what I mean.

Korean use the part of Western date format but not the same.

I need below date formats. "/" can be "-" or ignored in the documents. YYYY-MM-DD or YYYYMMDD.

• YY/MM/DD
• YYYY/MM/DD
• MM/DD
• MM/DD (NN)
• YY년 M월 D일
• YYYY년 M월 D일
• YY"년도 제"Q"사분기"
• M월 D일

Korean use hanja(kanji) and I think the date format is similar but not the same in Japan and Chinese(e.g. Era) .
You can see the Korean format more in LO directly.

[kjambunathan]

Styles can now be specified using nxml-mode blocks. This means one can use the full power of Org Babel to generate complex documents.

For a sample document with auto-generated page header and footer, see #180 (comment)