Re: Org-mode notes about school lessons

[Jean Louis]

* Sébastien Gendre  [2023-02-24 15:58]:
> For each lessons, I need to note:
> - Name
> - Schedule
> - Classroom
> - Teacher name and e-mail
> - Assistant name and e-mail
> - URL to the web page of this lesson on our online learning website
> - List of all distributed documents
> - Note on each of the distributed documents
> - Lesson plan
> - Notes taken in classroom while the teacher speak
> - Notes taken while doing the practice work
> - Tasks asked by the teacher

Here is the solution with Org:
--

* People
** Teachers
*** Mr. Evil
:PROPERTIES:
:ID:   067030f3-b833-4559-8159-6f94913a5408
:E-MAIL:   mre...@example.com
:END:
** Assistants
*** Mini Me
:PROPERTIES:
:ID:   894a5fe6-f694-44c6-9285-b1fa7727e6c9
:E-MAIL:   min...@example.com
:END:
* Classrooms
** Classroom #1
   :PROPERTIES:
   :ID:   23a3959a-19af-4890-a4de-16aff843f3a8
   :END:
** Classroom #2
   :PROPERTIES:
   :ID:   891d563d-96f8-47a5-b7cd-4d4565cf1524
   :END:
* Lessons
** My lesson name
   :PROPERTIES:
   :CLASSROOM: 23a3959a-19af-4890-a4de-16aff843f3a8
   :TEACHER:  067030f3-b833-4559-8159-6f94913a5408
   :ASSISTANT: 894a5fe6-f694-44c6-9285-b1fa7727e6c9
   :URL:  https://www.example.com/my-lesson-name
   :END:

*** Distributed documents
 My document one
Notes here about the document one
 My document two
Notes here about the document two

*** Lesson Plan

*** Notes taken in classroom while the teacher speak
*** Notes taken while doing the practice work
*** TODO Tasks asked by the teacher

---
What I would do for the above referencing system is representation or "jump" 
function, so that when you have something like this:

** My lesson name
   :PROPERTIES:
   :CLASSROOM: 23a3959a-19af-4890-a4de-16aff843f3a8
   :TEACHER:  067030f3-b833-4559-8159-6f94913a5408
   :ASSISTANT: 894a5fe6-f694-44c6-9285-b1fa7727e6c9
   :URL:  https://www.example.com/my-lesson-name
   :END:

That I can quickly see which classroom is that or which teacher is that.

(defun rcd-org-uuid-name ()
  "Display name for referenced Org UUID."
  (interactive)
  (let* ((uuid (thing-at-point 'uuid))
 (found (org-id-find uuid))
 (heading))
  (when (and found uuid)
(save-excursion
  (goto-char (cdr found))
  (setq heading (org-get-heading)))
(message "%s" heading

When you move cursor to one of those UUIDs, you would see "Mini me" in
the mini buffer. Or you wish to jump there by UUID:

(defun rcd-org-uuid-jump ()
  "Go to heading of the referenced Org UUID."
  (interactive)
  (let* ((uuid (thing-at-point 'uuid))
 (found (org-id-find uuid))
 (heading))
  (when (and found uuid)
(goto-char (cdr found)

The referencing system can enable to make reports on each lesson where
names of people and other attributes are nicely displayed. When you
change the heading or name of the teacher, the report would get
automatically updated.

> Thirdly, I need to manage the projects that teachers ask us to do. With 
> deadlines.
> 
> * What I plan to do
> 
> As I need to write a lot for each lesson, and each lesson are mostly
> independent from each other, I plan to have 1 file per lesson.
> 
> In each file, I plan to have the same structure:
> - General information
> - Tasks and Projects
> - Distributed documents
> - Notes

You need not have one file per lesson, you can write it all in one single file.

> In "General information", I put the schedule of the lesson, the
> classroom, the teacher and assistant name and e-mail and the URL to our
> online platform.
> 
> In "Tasks and Projects", I put all work the teacher ask us to do. For
> each, an Org-mode sub-headline with a TODO status. A project is just a task
> with sub-tasks. Or maybe have a PROJECT status ?

I do not agree to the hierarchy how you specified, as I am used to
military style:

1. Plan

2. Programs, belong to plan

3. Projects, they are one step of a plan, when that step cannot easily
   be executed

4. Orders are tasks, or steps of programs or projects

But I cannot see how "Project" is subsection of a "Task", as task is
often something very specific. Though in other definitions task can be
project too. I just say it is not common, though you can mix terms as
you wish.

> * What I miss
> 
> There is some point I'm note sure on what or how to do it.
> 
> First, the tasks. I don't know If it's better to keep them in the lesson
> org file or move them with all my other tasks (home and work). I think
> to include them in the org-agenda, so I can have global view of all ma
> tasks. From school, work and home.

Yes, and that works.

> Second, the weekly schedule. Is it better to have a column view on a
> separate file or to see the all the lessons in my org-agenda ? In the
> first case, is it possible to build a column view from different file ?
> In the second case, how to do it and to manage vacations ?

You already got it, how I see it. It is possible to use multiple files

Re: [BUG] `(org-agenda-list)` doesn't respect the `org-agenda-start-day` when `org-agenda-span` is equal to 7. [9.6.1 (release_9.5.5-1519-gaa2249 @ /home/rmnull/lab/libre/org-mode/lisp/)]

[rmnull]

Sorry about filling an existing bug without checking the updated docs.
And Thanks for pointing out the fix.

On 27 February 2023 5:08:42 pm UTC, Ihor Radchenko  wrote:
>rmn...@posteo.net writes:
>
>
>> * One Line summary
>> `org-agenda-list` shows the week agenda list, instead of respecting 
>> the org-agenda-start-day when the org-agenda-span is 7.
>
>Thanks for reporting!
>This sounds similar to 
>https://list.orgmode.org/orgmode/62a2389f-cf1f-9caa-7266-015f3e05d...@gmail.com/
>
>-- 
>Ihor Radchenko // yantar92,
>Org mode contributor,
>Learn more about Org mode at .
>Support Org development at ,
>or support my work at 

[DISCUSS] "same text-property competing" problem in external packages

[stardiviner]

I got a problem when more than one Emacs package competing on setting
text-property on same target from different packages.

Here is the original problem and discussion link:
https://github.com/nobiot/org-transclusion/issues/166

Does anybody have a good idea to solve this problem?

Thanks for your idea and suggestions.

[stardiviner] GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter:  @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36  CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/

Re: Bug or expected behavior? org-sparse-tree visibility toggling

[Cassio Koshikumo]

Hm. It makes sense that TAB is not affected... Somehow I hadn't really
considered that.

What I expected to happen (and now I realize it was not a justified
expectation) was to have the visibility of the sparse-tree kept while
tabbing. So I could expand a tree, then collapse it again, all the
while keeping the sparse-tree "filter" applied. But I guess it doesn't
make much sense.

Well, I guess I could leave it as a suggestion for new functionality,
but I don't even know if it's feasible.

Thanks!


On Sun, Feb 26, 2023 at 8:52 AM Ihor Radchenko  wrote:
>
> Cassio Koshikumo  writes:
>
> > Create an .org file with the following contents:
> >
> > * First Level
> > ...
> > Now, C-c / m (or M-x org-sparse-tree and select m) and Match: tag.
> >
> > The resulting sparse tree looks like this:
> >
> > * First Level
> > ** One :tag:
> > *** Child
> > ** Four :tag:
> >
> > So far, so good. Now, put point on heading One and press TAB. Child is 
> > hidden.
> >
> > The problem: press TAB again. Now Two and Three are also shown,
> > effectively breaking the sparse tree filtering. (Actually Five is
> > shown, too, it seems...)
>
>  is not affected by sparse tree.
> Sparse tree just reveals headings that match certain criteria and
> highlights them.
>
> May you describe what you expected to happen?
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 



-- 
Cassio Koshikumo

Re: [BUG] Org-reveal and setupfile conflict [9.6.1 (9.6.1-gaa48c8)]

[Ihor Radchenko]

Joshua Lambert  writes:

> 1. With the following Org file open, it should export the Org Reveal
> slides fine.
> 2. After you add the following line to that Org file after the title,
> try exporting and viewing the Org Reveals slides again. This time, their
> text is too big in the unnumbered lists. I think the CSS from the two export
> methods seems to be clashing.
>
> #+setupfile: 
> https://fniessen.github.io/org-html-themes/org/theme-readtheorg.setup

What you see is expected because org-reveal recognizes and uses
HTML_HEAD in https://github.com/yjwen/org-reveal/blob/master/ox-reveal.el#L1411

Canceled.

As a workaround, you can modify INFO alist removing the value of
:html-head and :html-head-extra properties when exporting via org-reveal
in :filter-parse-tree.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] lisp/ob-screen.el: Support ~:var~ header args for babel blocks

[Ihor Radchenko]

Ken Mankoff  writes:

>> To archive this, you can define a full
>> org-babel-variable-assignments:screen function that does what I
>> described.
>
> You're pushing my lisp skills here. Which is fine, but I might need some help.
>
> In ob-shell I see
>
> (defcustom org-babel-shell-names
>   '("sh" "bash" "zsh" "fish" "csh" "ash" "dash" "ksh" "mksh" "posh")
>
> Should I create a function that, using case statement or something similar, 
> checks for each of these and calls that flavor? I think I could do that.

Not each of these. AFAIU, :cmd header property in ob-screen defines
which shell to use. Knowing shell name, you can deduce the function name
to be used for variable assignments. See how it is done in
`org-babel-expand-src-block'.

> But if I also see org-babel-shell-initialize in ob-shell that looks like it 
> creates defaliases for each of these to (org-babel-execute:shell) and 
> #'org-babel-variable-assignments:shell.

The convention is for every possible #+begin_src lang to have
org-babel-variable-assignments:LANG.
ob-shell just tries to avoid unnecessary code duplication and instead of
writing identical org-babel-variable-assignments:sh
org-babel-variable-assignments:bash, org-babel-variables-assignents:zsh,
..., it generates them using a macro.

> I'm not sure how that is very different from what I've done. I'm not sure 
> what to do here, nor how to do what you suggest (yet - I've only read it so 
> far, not spent a lot of time experimenting and searching, so I may be able to 
> implement what I think is a solution to what you wrote, but I doubt it'll be 
> what you expect).

AFAIU, you don't need to juggle with macros as ob-shell does. Something
similar to `org-babel-expand-src-block' will do.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [POLL] Naming of "export features"

[Ihor Radchenko]

Sébastien Miquel  writes:

>> The proposed template system will provide more flexibility to modify the
>> default export transcoders.
>
> Reading your original proposal, I see nothing that provides more
> flexibility. I can guess at how it would allow one to prepend/append
> stuff to the output of the default transcoder. Anything more flexible
> than that would require breaking these default transcoders into parts,
> which you did not originally mention.

Here is my refined proposal, which we converged to upon further
discussion with TEC. Basically, we will extend the notion of export
transcoder to be a list instead of a function:

:translate-alist
'(...
  (table :snippets ((table-begin :when caption :snippet "\\begin{table}[htbp]")
(caption :snippet (format "\\caption{%s}" ()))
(centering :snippet "\\centering")
(tabular-begin :snippet (format "\\begin{tabular}%s" 
))
(contents :snippet )
(tabular-end :snippet "\\end{tabular}")
(table-end :when caption :snippet "\\end{table}")
  :conditions ((t . table-begin centering table-end tabular-begin 
contents tabular-end)
   ((lambda (el info) (org-element-property :caption el)) . 
caption)))
...)

>>> Here's a couple interesting examples that currently cannot, I think.
>>>+ a `multicol` heading property, that wraps the content of the
>>>  heading in a multicol environment.
>> Could you please illustrate with examples?
>
> Exported content would be:
> #+BEGIN_SRC latex
> \section{ABC}
> \begin{multicols}{3}
>Section content
> \end{multicols}
> #+END_SRC

With new template system, it will be very easy. You just need to add new
elements to the section template:

By default:

(section :snippets ((contents :snippet (lambda (_ _ contents) contents

You can just add

:snippets
(wrap-multicol-begin :before contents :snippet "\\begin{multicols}{3}")
(wrap-multicol-end :after contents :snippet "\\end{multicols}")

:conditions (t . wrap-multicol-begin wrap-multicol-end)


>>>+ a `nocontent` property that do not export the content of the
>>>  heading
>> This can be done with :filter-parse-tree or :filter-headline
>
> I guess. This isn't "couple of lines"-easy though.

Sure. With new system, it will be just

:snippets (section)
(prevent-contents :prevents contents)
:conditions
(t . prevent-contents)

> See higher. More flexibility requires breaking up some transcoders
> into pieces. AFAIU it, the proposal you originally described does not
> bring any more flexibility beyond what can be done through short
> advices, or indeed the `:filter-` functions. I'm not sure this
> dedicated syntax is preferable to advices.

I hope that the above examples clarified things.
As you can see, it is possible to manipulate the order of elements in
the original templates and disable some existing parts quite easily.

Of course, we will first need to rewrite built-in transcoders into
templates. Most of them can be rewritten rather trivially, fortunately.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: ox-rst still working?

[Angel de Vicente]

Ihor Radchenko  writes:
> I just meant that if you have org-ref installed, it may override the
> ox-rst menu item. There is a way to solve this, but I am not sure if the
> problem is originated from this guess of mine.

Ah, ok. No, I don't have org-ref installed.

-- 
Ángel de Vicente
 Research Software Engineer (Supercomputing and BigData)
 Tel.: +34 922-605-747
 Web.: http://research.iac.es/proyecto/polmag/

 GPG: 0x8BDC390B69033F52


smime.p7s
Description: S/MIME cryptographic signature

Re: [PATCH] Introduce "export features"

[Ihor Radchenko]

Sébastien Miquel  writes:

> Ihor Radchenko writes:
 The traditional user-facing approach for toggling staff in export is
 setting export options.
>>> Indeed. Then I suggest that such use be described in the manual.
>>> Having the user create a whole new option in order to toggle a
>>> `chikenize` package seems a bit unwieldy, however.
>> What do you suggest instead of creating a new option?
>
> Timothy's patch supports having a feature depend on a variable. I was
> thinking here of a user variable (instead of an already defined org
> variable) that could be toggled per document.
>
> It is fairly orthogonal to the original purpose of the patch, but it
> does scratch an annoying itch of mine: there's very little support in
> org to minutely tweak the export on a per document basis, beyond the
> default options.

Defining a new option is easy:

(org-export-define-derived-backend 'my-html 'html
  :options-alist
  '((:my-option "MY_OPTION_KEYWORD" nil "my-option" my-option-variable)))

Then, you can either

#+:BIND: my-option-variable t
or
#+OPTIONS: my-option:t
or
#+MY_OPTION_KEYWORD: t

Of course, you will also need to plug support of :my-option as needed
via filters or altering transcoders.

Timothy, since you are going to provide a macro for altering the
existing backends, it would also make sense to generalize it for
altering other aspects of the backends, like option-alist,
filters-alist, and menu-entry.

> One way to do this (easier than setting up a new option), is to define
> any variable, make the feature depend on it, and set it using the
> `#+bind` keyword. Combined with these export features, this could be
> used to easily tweak the LaTeX preamble, per document.
>
> If we find this use case to be legitimate and useful, I suggested
> earlier making it even easier with a `#+org_export_features` keyword.
> It would only take a list of feature names, and not require any
> variable tied to the feature.

I do not see much point compared to option alist, which is more
flexible. And you can always define a feature with condition to match
against "#\\+org_export_features.+my-feature".

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: ox-rst still working?

[Ihor Radchenko]

Angel de Vicente  writes:

>> Note that ox-rst menu clashes with default org-ref menu.
>
> Not sure what to make out of this. I guess this is the problem in my
> side, but how do you use the ox-rst menu then (or you don't use the
> dispatcher menu and invoke directly the rst export command?)

I just meant that if you have org-ref installed, it may override the
ox-rst menu item. There is a way to solve this, but I am not sure if the
problem is originated from this guess of mine.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] ox-md image captions

[Ihor Radchenko]

Vladimir Alexiev  writes:

> I have an image caption like this:
>
> #+label: fig:bsdd-graphql-voyager-refact-detail
> #+caption: Refactored bSDD GraphQL Schema
> [[./img/bsdd-graphql-voyager-refact-Classification-ClassificationProperty.png]]
>
> ox-md exports it like this:
>
> ![img](./img/bsdd-graphql-voyager-refact-Classification-ClassificationProperty.png
> "Refactored bSDD GraphQL Schema")
>
> (see https://git.sr.ht/~bzg/org-mode/tree/main/item/lisp/ox-md.el#L595)
>
> However, pandoc expects image captions to be formatted like this:
>
> ![Refactored bSDD GraphQL
> Schema](./img/bsdd-graphql-voyager-refact-Classification-ClassificationProperty.png)

The current ox-md's behaviour has been introduced in 87b48e5a2824:

ox-md: Fix image transcoding

* lisp/ox-md.el (org-md-link): Do not confuse caption and alt-text.
  Provide "img" as default alt-text.

 ...
 ... format "![img](%s)" ...

However, looking at
https://www.markdownguide.org/basic-syntax#adding-titles

You can optionally add a title for a link. This will appear as a
tooltip when the user hovers over the link. To add a title, enclose
it in quotation marks after the URL.

So, img is not really alt text, but the opposite.
The commit appears to be inaccurate.

I am inclined to change ![img](url "caption") to
![caption](url) for links without description (links with description do
not obey caption in org export).

Any objections?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

visual-line-mode don't play well with org-latex-preview

[chris]

Hi all,

```
hello hello hello hello hello hello hello hello hello hello hello hello hello 
hello hello  \(\text {hello hello hello hello hello hello hello hello}\)
```

If you put the above text in a org file, and activate `visual-line-mode` and 
`org-latex-preview`, depending on the length of the initial part of the text, 
the generated png/svg image from latex expression can be displayed in full, 
partially hidden or totally hidden.

That certainly hinder readability.

I've search the web to see if someone else did stumbled on that but haven't 
found anything yet.

Sure enough there isn't an obvious fix that would deal with every cases, like 
when the image is longer that the width of the window of the max column of 
`visual-column-mode`. At least there are different cases to consider.

Best,
Chris

Re: [BUG] `(org-agenda-list)` doesn't respect the `org-agenda-start-day` when `org-agenda-span` is equal to 7. [9.6.1 (release_9.5.5-1519-gaa2249 @ /home/rmnull/lab/libre/org-mode/lisp/)]

[Ihor Radchenko]

rmn...@posteo.net writes:


> * One Line summary
> `org-agenda-list` shows the week agenda list, instead of respecting 
> the org-agenda-start-day when the org-agenda-span is 7.

Thanks for reporting!
This sounds similar to 
https://list.orgmode.org/orgmode/62a2389f-cf1f-9caa-7266-015f3e05d...@gmail.com/

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: inconsistency with :eval yes in orgmode.org and gnu.org manuals for org 9.6, 9.5?

[Ihor Radchenko]

Dan Drake  writes:

> It seems like ":eval yes" was removed some time ago -- see
> https://emacs.stackexchange.com/a/3570/19526.
>
> Did that get re-added? It seems like it was replaced by the
> org-confirm-babel-evaluate mechanism --
> https://www.gnu.org/savannah-checkouts/gnu/emacs/manual/html_node/org/Code-Evaluation-Security.html.

It did not really get removed.
But its meaning indeed changed slightly, despite what the current manual
says.

:eval yes evaluates the code blocks, but not unconditionally. It still
obeys org-confirm-babel-evaluate.

Does the attached patch clarify the situation?
>From 3867672d6b38b3c0ccba0b5da8e4a3adb7f111b1 Mon Sep 17 00:00:00 2001
Message-Id: <3867672d6b38b3c0ccba0b5da8e4a3adb7f111b1.1677517512.git.yanta...@posteo.net>
From: Ihor Radchenko 
Date: Mon, 27 Feb 2023 20:02:50 +0300
Subject: [PATCH] org-manual: Clarify that :eval yes obeys
 `org-confirm-babel-evaluate'

* doc/org-manual.org (Limit code block evaluation): Clarify :eval yes
value.

Reported-by: Dan Drake 
Link: https://orgmode.org/list/cakqbaefrgdzqqqkxhkvdptgm7nyybwgxpjj3yorknud2bsw...@mail.gmail.com
---
 doc/org-manual.org | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 6a625b42a..1c97d6aa8 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -18123,7 +18123,8 @@ *** Limit code block evaluation
 
 - =yes= ::
 
-  Org always evaluates the source code without asking permission.
+  Org evaluates the source code, possibly asking permission according
+  to ~org-confirm-babel-evaluate~.
 
 - =never= or =no= ::
 
-- 
2.39.1


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: ox-rst still working?

[Angel de Vicente]

Hello,

Ihor Radchenko  writes:

> Works on my side with the latest Org.

thanks for the update.

> Note that ox-rst menu clashes with default org-ref menu.

Not sure what to make out of this. I guess this is the problem in my
side, but how do you use the ox-rst menu then (or you don't use the
dispatcher menu and invoke directly the rst export command?)

Cheers,
-- 
Ángel de Vicente
 Research Software Engineer (Supercomputing and BigData)
 Tel.: +34 922-605-747
 Web.: http://research.iac.es/proyecto/polmag/

 GPG: 0x8BDC390B69033F52


smime.p7s
Description: S/MIME cryptographic signature

[BUG] ox-md image captions

[Vladimir Alexiev]

I have an image caption like this:

#+label: fig:bsdd-graphql-voyager-refact-detail
#+caption: Refactored bSDD GraphQL Schema
[[./img/bsdd-graphql-voyager-refact-Classification-ClassificationProperty.png]]

ox-md exports it like this:

![img](./img/bsdd-graphql-voyager-refact-Classification-ClassificationProperty.png
"Refactored bSDD GraphQL Schema")

(see https://git.sr.ht/~bzg/org-mode/tree/main/item/lisp/ox-md.el#L595)

However, pandoc expects image captions to be formatted like this:

![Refactored bSDD GraphQL
Schema](./img/bsdd-graphql-voyager-refact-Classification-ClassificationProperty.png)

(see https://pandoc.org/MANUAL.html#images).
Consequently, all my captions are lost and replaced with "img".

Maybe ox-md should emit captions in both places?

![caption](image-url "caption")

Note: I checked, ox-gfm doesn't do anything different regarding image
captuions

---

[9.5.2 (release_9.5.2-25-gaf6f12 @ c:/Emacs/share/emacs/28.1/lisp/org/)]
Emacs  : GNU Emacs 28.1 (build 52, x86_64-w64-mingw32) of 2022-04-04
Package: Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
c:/Emacs/share/emacs/28.1/lisp/org/)

Re: Hiding citations

[András Simonyi]

Dear All,

On Sat, 25 Feb 2023 at 18:19, M. ‘quintus’ Gülker
 wrote:

> Not yet, and it certainly looks nice, but the CSL style I use uses
> footnotes, and those are quite verbose. Rendering them (or rather, their
> content) into the text would expand it even more.

there is no assumption that the CSL style used for rendering should be
identical to the one used for export,
in fact, the default is just to use Chicago author-date. I typically
use it with an even more compressed author-date style.

best wishes,
András

>   -quintus
>
> --
> Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite
> Passau, Deutschland  | kont...@guelker.eu| O<
>