false-positive alert in the report to the CLI for .org with UUID

[nbehrnd]

Your application indicates a problem to the CLI when processing .org with UUID though the content intended safely reaches Anki.

In the setup I use, headers of sections are automatically get an UUID when calling C s to safe the file in Emacs. This useful optional feature is presented e.g., in a lesson by Rainer Koenig (video installment, blog post) and yields entries in the pattern of

* examples by A
  :PROPERTIES:
  :ID:       5fc8dc5f-5021-4149-9376-8066464ce7d6
  :END:
** Amiens
   :PROPERTIES:
   :ID:       c7d790bf-0efa-4502-911a-10fb66bce135
   :END:

With an open instance of Anki in Debian bookworm, the CLI reports your application encountered the property drawers as something different as if there were an error in the file to process. This alarm however is false positive:

$ org_to_anki anki2org_with_UUID.org 
file is  anki2org_with_UUID.org
Current line is not recognised: b'  :PROPERTIES:'
Current line is not recognised: b'  :ID:       5fc8dc5f-5021-4149-9376-8066464ce7d6'
Current line is not recognised: b'  :END:'
Current line is not recognised: b'   :PROPERTIES:'
Current line is not recognised: b'   :ID:       c7d790bf-0efa-4502-911a-10fb66bce135'
...

Suggestion: the UUID always are included in a block starting by the string :PROPERTIES: and closing by :END:. So one could imagine them as a switch to toggle on/off reading of the content of the .org for purpose to relay information to Anki.

*) Of course this can be switched off, e.g., by launching Emacs by

emacs -q

then however no longer enjoying local adjustments the user profile provides.

Observations refer to Anki (2.1.54 (b6a7760c)⁩) and your application running (version 0.2.1) in Linux Debian 12/bookworm (currently branch testing).

anki2org_with_UUID.org.zip