Accent color broken in pdfa
Opened this issue · 2 comments
Hi,
With the newest release the accent colors are not depicted correctly when pdfa=true in tudapub (colors are brighter than they should be).
It's a combination of versions if you use the current template setup using the \DocumentMetadata command instead of the option it works fine, e.g.
tuda_latex_templates/examples/DEMO-TUDaThesis-en.tex
Lines 35 to 38 in 03ad5b7
The bug was created as I pass the option now after the package is loaded… which is totally my fault. I am on that atm.
Issue here is that pdfx tries to convert colors to rgb but we need RGB as TUDa does not offer rgb values here.
If using the \DocumentMetadata setup is not an option you can add
\PassOptionsToPackage{RGB}{xcolor}
before \documentclass
It's a combination of versions if you use the current template setup using the
\DocumentMetadatacommand instead of the option it works fine, e.g.tuda_latex_templates/examples/DEMO-TUDaThesis-en.tex
Lines 35 to 38 in 03ad5b7
Does this produce a valid PDF/A (for TUbama) for students to submit their theses? Until a few months back, there was the option pdfa=true set within the templates and I see that this is now gone.
The problem is that the ShareLaTeX instance of the HRZ still uses v3.36 of your package (see #472 (comment)) and a lot of our students use it to write their theses.
Since about a week or two ago, a student of mine reported that the colors of the rendered PDF produced by the ShareLaTeX instance of the HRZ were wrong again (despite using your workaround with \DocumentMetadata) if pdfa=true was set.
When setting pdfa=false explicitly, the colors look accurate, but I do not want the students to get in any trouble when they submit their theses in TUbama.
As a check, I've used the example documents of the latest v3.40 release from GitHub and created a new project on said ShareLaTeX instance. Without setting pdfa=false, I cannot get the colors to look right. Did I miss something here?