Support unicode chars in annotations#20356
Conversation
|
@biagas and/or @JustinPrivitera if you can take a brief look and lemme know what you think so far, that would be great. I am deciding what to do about 3D axes because they have a lot of custom coding. |
| std::string fontFile = GetVisItResourcesDirectory(VISIT_RESOURCES_FONTS) + | ||
| VISIT_SLASH_STRING; | ||
|
|
||
| // Treat Arial as the "Regular" form of DejaVuSans |
There was a problem hiding this comment.
Can you elaborate on what these comments mean? What is the regular/mono/serif form of DejaVu and why are they mapped to Arial, Courier, and Times?
There was a problem hiding this comment.
These are different styles (behaviors) of fonts. Arial is a sans-serif (e.g. no serifs) font. Times is a serif font. Neither Arial or Times are "monospaced" (meaning columnar in that every character takes up the same space) like Courier which is often desired for displaying lines of code. My strong belief is that Arial, Times and Courier were used in VTK (long ago and still in our interface today) as recognizeable synonyms for those key font attributes.
There was a problem hiding this comment.
It just seems odd to me to have synonyms instead of the real thing.
There was a problem hiding this comment.
You asked what "regular/mono/serif" are. Does that suggest you are not as familiar with that font-speak? If so, don't fret. Most people don't. But, most people do know what Arial (or Helvetica), Times and Courier font faces are. I think that made sense for VTK way back when and I think it still probably makes sense in our GUI. Though, I could probably easily be convinced otherwise.
There was a problem hiding this comment.
Does that suggest you are not as familiar with that font-speak?
That's right. Thanks for explaining! I don't have a strong opinion here.
Co-authored-by: Justin Privitera <35237779+JustinPrivitera@users.noreply.github.com>
Co-authored-by: Justin Privitera <35237779+JustinPrivitera@users.noreply.github.com>
|
Sorry, I misclicked and merged develop into this branch. Hope that's ok. |
|
Ok, I finally have a viable path for unicode in the axes titles... Screen.Recording.2025-05-06.at.4.51.03.PM.mov |
…av/visit into feat-mcm86-10apr25-unicode-fonts
|
Unicode characters in file path names... Current VisIt
This Pull Request
|
…av/visit into feat-mcm86-10apr25-unicode-fonts
|
Hi @markcmiller86 ! |
|
@marcdurant apologies that I have let this languish. I worked through a lot of issues but only for 2D annotations. When I went to tackle 3D annotations, I ran into a number of snags that I was working through. The relevant VTK 9.5 objects were not working with VisIt's rendering modality and never actually appearing in a VisIt window. Though, the very same objects in a stand-alone VTK app worked fine. In addition, I've only recently re-activated the mac development platform that I was originally doing this work on and my attentions have been on getting a solid, new release of Silo out. I expect to be able to return to this in another month, maybe a tad sooner. |
|
@markcmiller86 Thanks for the update. Our specific use case is using Expressions to create new Curve variables, and we'd like to be able to label the plot in a way that more cleanly expresses the underlying Expression. |
4 participants
Description
Resolves #20350
Type of change
[ ] Bug fix[ ] Documentation update[ ] OtherHow Has This Been Tested?
Reminders:
Checklist: