-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
U+22BB \veebar: ⊻ #532
Comments
Hey, I created ⊻ based on the existing ∨ for a book project at Language Science Press. The changes are not upstream in this repository and need to be merged once someone with merging powers becomes active again. In the meantime, you could this compiled OTF: https://github.com/langsci/349/blob/main/LibertinusMath-Regular.otf Here's a minimal TeX document to use that symbol: \documentclass{article}
\usepackage{unicode-math}
\setmathfont{LibertinusMath-Regular.otf}
\begin{document}
$\veebar$
\end{document} The Libertinus package for the TeX distributions is managed by Herbert Voß. I'm sure that Herbert would be happy to update the sources once a new release from Libertinus becomes available – maybe this new release will include the ⊻ glpyh. You could also merge the code I used into your local sfd font sources:
|
@kopeckyf thanks so much!! |
Is there an open PR for this that you could point to, for the record? |
@waldyrious not yet, I thought I'd wait until the excellent #454 is merged. The eventual PR should not only include ⊻, but maybe also ⩒, ⊼ and some other math glyphs I've been working on. |
Pull request #568 now open for this glyph. |
Hey, thanks for the great font!
I think it'd be nice to have ⊻, an alternative to \oplus for xor. It's the default xor operator in Julia, for example. I noticed it didn't show up in the LaTeX package (by the way, how does the LaTeX package get updated? should I file this issue somewhere else too?) but it doesn't seem to be in the regular font either.
I'd love to help but I have no experience designing fonts and am worried I'd make something ugly :P
The text was updated successfully, but these errors were encountered: