From: "Juan Manuel Macías" <firstname.lastname@example.org> To: orgmode <email@example.com> Subject: Preview fonts from Dired with org-latex-preview (and test opentype features) Date: Mon, 10 Jan 2022 16:47:51 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) [-- Attachment #1: Type: text/plain, Size: 1339 bytes --] Hi, I have written for my personal use this code (still quite crude) that allows me to preview with org-latex-preview small text strings in a font marked in dired, and test open type features too. The preview is compiled with LuaLaTeX, since LuaTeX allows to load fonts that are not installed in the system. When a font is selected, the list of opentype features included in the font are extracted (using the otfinfo command), and they are arranged in the preview buffer as buttons. By clicking on each button we can activate in the preview the corresponding opentype feature. For example, if the font includes the 'smcp' feature, clicking on the button 'smcp' the text will be displayed in small caps. We can enter the text strings literally or through Unicode code: each character separated by a space; the separation between words is marked with a vertical bar. For example, this code: 0063 006f 0064 0065 | 0068 0065 0072 0065 returns the string "code here". As a third option, a complete specimen can be displayed from a file. Here is a demo video: https://cloud.disroot.org/s/aHXKiof36fTSZGB As I said, my function is still pretty crude, and while it works well, it's now more of a proof of concept than a finished thing. But if anyone wants to try it, I attach the code here in an org document. Best regards, Juan Manuel [-- Attachment #2: font-preview.org --] [-- Type: application/vnd.lotus-organizer, Size: 10258 bytes --]
next reply other threads:[~2022-01-10 17:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-10 16:47 Juan Manuel Macías [this message] 2022-01-18 20:50 ` Ken Mankoff
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Preview fonts from Dired with org-latex-preview (and test opentype features)' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).