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

Motion PDF Export: export without pre-selected svg logo #3586

Open
MSoeb opened this issue Apr 18, 2024 · 2 comments · May be fixed by #4443
Open

Motion PDF Export: export without pre-selected svg logo #3586

MSoeb opened this issue Apr 18, 2024 · 2 comments · May be fixed by #4443

Comments

@MSoeb
Copy link

MSoeb commented Apr 18, 2024

Description: The motion PDF export is not possible with an SVG file that is to be output in the header, for example. The image won't be exported. However, other image formats can be used without any problems.

Reproduction:

  1. download https://upload.wikimedia.org/wikipedia/commons/b/b0/NewTux.svg file, for example
  2. Open a meeting
  3. open files and upload the the file
  4. mark the new file with one of the header options in the three-dot-menu
  5. open motions > create a motion > export it -> logo is not exported

What should happen:
It should be possible to use a svg file for header options.

@MSoeb MSoeb added the bug label Apr 18, 2024
@MSoeb MSoeb added this to the 4.2 milestone Apr 18, 2024
@MSoeb MSoeb changed the title Motion PDF Export: export miss svg logo Motion PDF Export: export without pre-selected svg logo Apr 18, 2024
@MSoeb MSoeb added the low label Apr 18, 2024
@reiterl reiterl added feature and removed bug labels Apr 19, 2024
@reiterl
Copy link
Member

reiterl commented Apr 19, 2024

At the moment, we don't support svg file in pdf export. See IMAGE_USABLE_FOR_PDF_MIMETYPE.
This is not a bug. Adding the support for svg requires some work, but I think could be possible with pdfmake.

@m-schieder
Copy link
Member

pdfmake supports svg. However, they are integrated differently than images. This also needs to be implemented.

@anbebe anbebe self-assigned this Nov 25, 2024
@anbebe anbebe linked a pull request Dec 3, 2024 that will close this issue
@rrenkert rrenkert modified the milestones: 4.2, 4.3 Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants