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

Generate image files for all figures in editable formats from lutaml #548

Open
3 tasks
ribose-jeffreylau opened this issue Nov 5, 2021 · 4 comments
Open
3 tasks

Comments

@ribose-jeffreylau
Copy link
Contributor

ribose-jeffreylau commented Nov 5, 2021

Description

This is a multipart task:

  • Allow processing of lutaml files using metanorma directives.
  • Allow specification of editable image formats for the rendered lutaml diagrams.
  • Render all lutaml diagrams to the specified image formats to a specific file path using a specific file naming scheme, detailed below.

File name specification (pseudo-regex)

$standardNumber ( - $partNumber )? _ed $editionNumber fig $figureNumber

Examples

Figures for the first edition of ISO 12345-1 should be named as such:

  • 12345-1_ed1fig1.dwg
  • 12345-1_ed1fig1.svg
  • 12345-1_ed1fig1.ai

For figure files in an annex (e.g. Annex A), they should be named as such:

  • 12345-1_ed1figA1.dwg
  • 12345-1_ed1figA1.svg
  • 12345-1_ed1figA1.ai
@ronaldtse
Copy link
Contributor

  1. LutaML diagrams can already be specified in Metanorma blocks using the LutaML commands defined in Metanorma-plugin-LutaML
  2. LutaML should be generating SVG images, not sure if that option is available.
  3. Metanorma provides a warning if the pattern does not match ISO DWG rules but does not do anything actively. We need to implement this only for the “packaged” file to be submitted.

@ribose-jeffreylau
Copy link
Contributor Author

@ronaldtse I see. I forgot why in my project I was using Makefile to generate the PNG from LutaML files instead of using the metanorma plugin... probably it was to make use of Make's build dependency feature.

@ronaldtse
Copy link
Contributor

The reason was legacy practice 😜 we used Makefiles before until we have the plugin. Just a matter of order of availability!

@ronaldtse
Copy link
Contributor

ronaldtse commented Nov 5, 2021

And yes, dependency tracking is something we still don’t have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants