Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding ODF 1.3 support to the ODF Toolkit #26

Open
svanteschubert opened this issue Jan 20, 2020 · 4 comments · May be fixed by #200
Open

Adding ODF 1.3 support to the ODF Toolkit #26

svanteschubert opened this issue Jan 20, 2020 · 4 comments · May be fixed by #200
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@svanteschubert
Copy link
Contributor

I have started a branch of the 0.9.0 version to support ODF 1.3.
but decided in discussions with Michael Stahl and Oliver Rau afterwards that it might be easier to have an ODF 1.3 support based solely on the upcoming ODF 1.0.0 version.
The reason for this is that 1.0.0 is the merge of a several-year-old merge form Open-XChange using ODFDOM for their backend of their new OX Documents.

In the following, I am starting a listing what needs to be fixed - this is likely being updated during the lifetime of this issue.
This documentation should be added to our SITE documentation to describe how to do an ODF version change in the future.

Changes expected so far:

  1. The generator project needs to generate new ODFDOM typed DOM classes from the new ODF XML schema/grammar files. These files need to replace the ODFDOM prior classes for elements and attributes.

  2. The generator tests have to be adopted to embrace ODF 1.3.

  3. The ODF Validator needs to have an ODF 1.3 instead of an ODF 1.2 option.

  4. The ODF templates within ODFDOM - being used when creating new documents from the scratch needs to be added to ODF 1.3.
    I did this usually by editing the XML within the ZIP using JEdit with its archive and its XML extension.

@svanteschubert svanteschubert added the enhancement New feature or request label Jan 20, 2020
@svanteschubert
Copy link
Contributor Author

For simplicity reason, we are not providing yet the support of multiple versions at the time or the transformation of one version to the other.
IMHO this functionality should be described at the specification level, explaining the differences to the prior ODF version in a way that transformations can be generated.

@svanteschubert
Copy link
Contributor Author

  1. The HTML form of the ODF specification has to be exchanged with all its images.
    Test the HTML specification - should already be done on TC level, but better be safe than sorry:
    5a: A broken link check should be done
    5b: OLE objects in the specification should have been exchanged with images, otherwise they won't be visible in the HTML version - for instance by taking a look at into the ODT if there are still OLE objects.
  2. The taglet module, which is doing insertions of in the ODFDOM JavaDoc to the HTML form of the ODF specification has to be updated to reference to a new specification.

@svanteschubert
Copy link
Contributor Author

NOTE: The current ODF 1.3 branch based on the master will be abandoned and new ODF 1.3 branch will be created for the 1.0.0 release branch.

@svanteschubert svanteschubert self-assigned this Jun 28, 2020
@svanteschubert svanteschubert added this to the 2.0.0 milestone Jun 30, 2020
@svanteschubert
Copy link
Contributor Author

There are 36 new feature/enhancement in ODF 1.3.
They are described in detail in the OASIS JIRA bugtracker, there is a query for ODF 1.3 feature/enhancment.

An overview of the changes from “Open Document Format for Office Applications (OpenDocument) v1.2”
can be found in the end/appendix of each ODF 1.3 specification part:

PS: I am about to start a GitHub for the OASIS TC to bundle tools for the specification & test documents at OASIS standard level.

@svanteschubert svanteschubert removed this from the 0.11.0 milestone Dec 12, 2022
@svanteschubert svanteschubert modified the milestones: 0.11.0, 0.12.0 Dec 21, 2022
@svanteschubert svanteschubert linked a pull request Dec 22, 2022 that will close this issue
@mistmist mistmist modified the milestones: 0.12.0, 0.13.0 Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants