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

Allow for text alignment flexibility within the definition of the TU Dresden Corporate Design #76

Open
MarkusLeyser opened this issue May 24, 2022 · 0 comments
Assignees
Milestone

Comments

@MarkusLeyser
Copy link

Hello,

The corporate design of the TU Dresden in its current state as of July 2021 (with minor changes in 2022) allows for an alignment of the text at the left edge of the logo (instead of the alignment at the lettering within the logo) for scientific posters as well as other documents with narrow formats or large amounts of text:

Bei schmalen Formaten oder großen Textmengen (z. B. Flyer oder Wissenschaftliches Poster) ist die Ausrichtung des Textes an der linken Kante des Bildelementes des Logos der TUD zulässig. (See CD-Manual page 21)

As far as I can see, in the tudscrposter class, the text can only be aligned to the lettering within the logo.

I refer here to a 2013 topic in the LaTeX forum: As mentioned there, the TU Dresden CD defines a fixed design grid for books, theses, etc.

For other paper sizes and contents, however, explicit flexibility has (meanwhile?) been included in the TU Dresden CD.

Hence the feature request: package option that causes text alignment to the left edge of the logo. However, by default the alignment should still be at the left edge of the text within the logo, i.e. the standard alignment defined by the CD.

TU Dresden unites researches from very diverse fields of research. Such a package option would be very valuable because it enables the tudscrposter class to better meet the design needs for posters in all reasearch areas.

Thank you very much for the time you invest in this project!

@mrpiggi mrpiggi self-assigned this May 24, 2022
@mrpiggi mrpiggi added this to the v2.07 milestone May 24, 2022
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