#lualatex — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lualatex, aggregated by home.social.
-
Illustration de la variation des fontes variables avec luamplib et de leur animation avec animate, Le jeudi 24 septembre 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/36347 #latex #lualatex #metapost #luamplib #fontesVariables #fontesOpentype #animation #gutenberg #visioConférence
-
Illustration de la variation des fontes variables avec luamplib et de leur animation avec animate, Le jeudi 24 septembre 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/36347 #latex #lualatex #metapost #luamplib #fontesVariables #fontesOpentype #animation #gutenberg #visioConférence
-
Illustration de la variation des fontes variables avec luamplib et de leur animation avec animate, Le jeudi 24 septembre 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/36347 #latex #lualatex #metapost #luamplib #fontesVariables #fontesOpentype #animation #gutenberg #visioConférence
-
Illustration de la variation des fontes variables avec luamplib et de leur animation avec animate, Le jeudi 24 septembre 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/36347 #latex #lualatex #metapost #luamplib #fontesVariables #fontesOpentype #animation #gutenberg #visioConférence
-
My new paper can now be found on the #arXiv (https://arxiv.org/abs/2608.19424), in addition to my website. I haven't posted to the arXiv in a little while and things have changed. I was glad to see that we don't need to supply bbl files anymore and can finally just submit bib files instead. It was also nice to see a choice of #TeXLaTeX compilers, but still no #LuaLaTeX, so I did have to cut the Japanese text from the paper. I did used to have a way to do this with #PDFLaTeX but the LuaLaTeX way is so much cleaner I don't even want to mess with the old way now.
I have mixed feelings about the arXiv. I wish I didn't feel like I had to post there for legitimacy or exposure, and things haven't gotten evil enough for me to bail, but I'm feeling like it's time to think about how to live without it. Posting papers to my website is a start, but it doesn't seem like the whole solution.
-
My new paper can now be found on the #arXiv (https://arxiv.org/abs/2608.19424), in addition to my website. I haven't posted to the arXiv in a little while and things have changed. I was glad to see that we don't need to supply bbl files anymore and can finally just submit bib files instead. It was also nice to see a choice of #TeXLaTeX compilers, but still no #LuaLaTeX, so I did have to cut the Japanese text from the paper. I did used to have a way to do this with #PDFLaTeX but the LuaLaTeX way is so much cleaner I don't even want to mess with the old way now.
I have mixed feelings about the arXiv. I wish I didn't feel like I had to post there for legitimacy or exposure, and things haven't gotten evil enough for me to bail, but I'm feeling like it's time to think about how to live without it. Posting papers to my website is a start, but it doesn't seem like the whole solution.
-
My new paper can now be found on the #arXiv (https://arxiv.org/abs/2608.19424), in addition to my website. I haven't posted to the arXiv in a little while and things have changed. I was glad to see that we don't need to supply bbl files anymore and can finally just submit bib files instead. It was also nice to see a choice of #TeXLaTeX compilers, but still no #LuaLaTeX, so I did have to cut the Japanese text from the paper. I did used to have a way to do this with #PDFLaTeX but the LuaLaTeX way is so much cleaner I don't even want to mess with the old way now.
I have mixed feelings about the arXiv. I wish I didn't feel like I had to post there for legitimacy or exposure, and things haven't gotten evil enough for me to bail, but I'm feeling like it's time to think about how to live without it. Posting papers to my website is a start, but it doesn't seem like the whole solution.
-
My new paper can now be found on the #arXiv (https://arxiv.org/abs/2608.19424), in addition to my website. I haven't posted to the arXiv in a little while and things have changed. I was glad to see that we don't need to supply bbl files anymore and can finally just submit bib files instead. It was also nice to see a choice of #TeXLaTeX compilers, but still no #LuaLaTeX, so I did have to cut the Japanese text from the paper. I did used to have a way to do this with #PDFLaTeX but the LuaLaTeX way is so much cleaner I don't even want to mess with the old way now.
I have mixed feelings about the arXiv. I wish I didn't feel like I had to post there for legitimacy or exposure, and things haven't gotten evil enough for me to bail, but I'm feeling like it's time to think about how to live without it. Posting papers to my website is a start, but it doesn't seem like the whole solution.
-
RE: https://techhub.social/@TeXUsersGroup/117074039342615609
Update to my #LuaLaTeX package "marginalia" (marginal notes anywhere, even where \marginpar does not work, with automatic adjustment of positions to prevent clashes).
It now supports right-to-left text and the document being bound on the right-hand side, in which case the terms "outer" and "inner" (used in options to specify the position of marginal notes, and styles, sizes, etc. of notes in different margins) are interpreted appropriately.
The new functionality has been tested, but I do not write any right-to-left language, so feedback would be welcome.
-
RE: https://techhub.social/@TeXUsersGroup/117074039342615609
Update to my #LuaLaTeX package "marginalia" (marginal notes anywhere, even where \marginpar does not work, with automatic adjustment of positions to prevent clashes).
It now supports right-to-left text and the document being bound on the right-hand side, in which case the terms "outer" and "inner" (used in options to specify the position of marginal notes, and styles, sizes, etc. of notes in different margins) are interpreted appropriately.
The new functionality has been tested, but I do not write any right-to-left language, so feedback would be welcome.
-
RE: https://techhub.social/@TeXUsersGroup/117074039342615609
Update to my #LuaLaTeX package "marginalia" (marginal notes anywhere, even where \marginpar does not work, with automatic adjustment of positions to prevent clashes).
It now supports right-to-left text and the document being bound on the right-hand side, in which case the terms "outer" and "inner" (used in options to specify the position of marginal notes, and styles, sizes, etc. of notes in different margins) are interpreted appropriately.
The new functionality has been tested, but I do not write any right-to-left language, so feedback would be welcome.
-
RE: https://techhub.social/@TeXUsersGroup/117074039342615609
Update to my #LuaLaTeX package "marginalia" (marginal notes anywhere, even where \marginpar does not work, with automatic adjustment of positions to prevent clashes).
It now supports right-to-left text and the document being bound on the right-hand side, in which case the terms "outer" and "inner" (used in options to specify the position of marginal notes, and styles, sizes, etc. of notes in different margins) are interpreted appropriately.
The new functionality has been tested, but I do not write any right-to-left language, so feedback would be welcome.
-
When I edit my books, hyphenations are checked, listed, and flagged as valid (or not) by my #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen].
Attached is an example of the draft layout with supplementary data I use when I am working on ‘An Annotated Mathematician’s Apology’ [https://archive.org/details/hardy_annotated].
The actual page is shown in the frame, with the status flags next to each hyphenation. Above is the version and git commit the PDF was compiled from. To the right is a list of the various index entries that point to this page.
-
When I edit my books, hyphenations are checked, listed, and flagged as valid (or not) by my #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen].
Attached is an example of the draft layout with supplementary data I use when I am working on ‘An Annotated Mathematician’s Apology’ [https://archive.org/details/hardy_annotated].
The actual page is shown in the frame, with the status flags next to each hyphenation. Above is the version and git commit the PDF was compiled from. To the right is a list of the various index entries that point to this page.
-
When I edit my books, hyphenations are checked, listed, and flagged as valid (or not) by my #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen].
Attached is an example of the draft layout with supplementary data I use when I am working on ‘An Annotated Mathematician’s Apology’ [https://archive.org/details/hardy_annotated].
The actual page is shown in the frame, with the status flags next to each hyphenation. Above is the version and git commit the PDF was compiled from. To the right is a list of the various index entries that point to this page.
-
When I edit my books, hyphenations are checked, listed, and flagged as valid (or not) by my #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen].
Attached is an example of the draft layout with supplementary data I use when I am working on ‘An Annotated Mathematician’s Apology’ [https://archive.org/details/hardy_annotated].
The actual page is shown in the frame, with the status flags next to each hyphenation. Above is the version and git commit the PDF was compiled from. To the right is a list of the various index entries that point to this page.
-
【鉄テキに匹敵】凝った tcolorbox の作り方【前編】（LaTeX確認シリーズ#６）
https://qiita.com/KKTeX/items/91efd16fd2e759dcc671?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
【鉄テキに匹敵】凝った tcolorbox の作り方【前編】（LaTeX確認シリーズ#６）
https://qiita.com/KKTeX/items/91efd16fd2e759dcc671?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
【鉄テキに匹敵】凝った tcolorbox の作り方【前編】（LaTeX確認シリーズ#６）
https://qiita.com/KKTeX/items/91efd16fd2e759dcc671?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
My #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen] has just been updated, and its name is now partly an artefact. :-)
It can now check each hyphenation in the document against a user-specified dictionary of valid divisions (or allowlist) and so list and/or visually flag either all of them or only those that do not match the dictionary. (And it handles multi-language documents.)
Attached is an example from the docs — a passage from Gibbon's ‘Decline and Fall’ set in narrow columns, with each hyphenation flagged as valid, invalid, ambiguous (in UK English ‘present’ hyphenates differently as a verb vs adj./noun), or unknown (the name ‘Vespasian’ isn't in the dictionary).
-
My #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen] has just been updated, and its name is now partly an artefact. :-)
It can now check each hyphenation in the document against a user-specified dictionary of valid divisions (or allowlist) and so list and/or visually flag either all of them or only those that do not match the dictionary. (And it handles multi-language documents.)
Attached is an example from the docs — a passage from Gibbon's ‘Decline and Fall’ set in narrow columns, with each hyphenation flagged as valid, invalid, ambiguous (in UK English ‘present’ hyphenates differently as a verb vs adj./noun), or unknown (the name ‘Vespasian’ isn't in the dictionary).
-
My #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen] has just been updated, and its name is now partly an artefact. :-)
It can now check each hyphenation in the document against a user-specified dictionary of valid divisions (or allowlist) and so list and/or visually flag either all of them or only those that do not match the dictionary. (And it handles multi-language documents.)
Attached is an example from the docs — a passage from Gibbon's ‘Decline and Fall’ set in narrow columns, with each hyphenation flagged as valid, invalid, ambiguous (in UK English ‘present’ hyphenates differently as a verb vs adj./noun), or unknown (the name ‘Vespasian’ isn't in the dictionary).
-
My #LuaLaTeX package "lua-list-hyphen" [https://ctan.org/pkg/lua-list-hyphen] has just been updated, and its name is now partly an artefact. :-)
It can now check each hyphenation in the document against a user-specified dictionary of valid divisions (or allowlist) and so list and/or visually flag either all of them or only those that do not match the dictionary. (And it handles multi-language documents.)
Attached is an example from the docs — a passage from Gibbon's ‘Decline and Fall’ set in narrow columns, with each hyphenation flagged as valid, invalid, ambiguous (in UK English ‘present’ hyphenates differently as a verb vs adj./noun), or unknown (the name ‘Vespasian’ isn't in the dictionary).
-
Big update to ‘Form & Number: A History of Mathematical Beauty’: the PDFs are now *tagged* (plus various minor improvements).
A #TaggedPDF contains hidden extra semantic information to assist screen-reading software etc., including alt text for diagrams+images (in the case of ‘F&N’, 552 pieces of alt text were required, some quite lengthy).
The new version is available (#OpenAccess as always) at: https://archive.org/details/cain_formandnumber_ebook_large
Feedback from users of screen readers would be very welcome!
Creating this version has been possible because of the ongoing LaTeX tagging project [https://latex3.github.io/tagging-project/] (thank you to the LaTeX team and other contributors!). I have been adapting my own #LuaLaTeX styles [https://codeberg.org/ajcain/minos] to use the new interfaces.
1/2
#accessibility #a11y #MathArt #HistMath #HistSci #MathematicalBeauty #aesthetics #typography #TeXLaTeX
-
Big update to ‘Form & Number: A History of Mathematical Beauty’: the PDFs are now *tagged* (plus various minor improvements).
A #TaggedPDF contains hidden extra semantic information to assist screen-reading software etc., including alt text for diagrams+images (in the case of ‘F&N’, 552 pieces of alt text were required, some quite lengthy).
The new version is available (#OpenAccess as always) at: https://archive.org/details/cain_formandnumber_ebook_large
Feedback from users of screen readers would be very welcome!
Creating this version has been possible because of the ongoing LaTeX tagging project [https://latex3.github.io/tagging-project/] (thank you to the LaTeX team and other contributors!). I have been adapting my own #LuaLaTeX styles [https://codeberg.org/ajcain/minos] to use the new interfaces.
1/2
#accessibility #a11y #MathArt #HistMath #HistSci #MathematicalBeauty #aesthetics #typography #TeXLaTeX
-
Big update to ‘Form & Number: A History of Mathematical Beauty’: the PDFs are now *tagged* (plus various minor improvements).
A #TaggedPDF contains hidden extra semantic information to assist screen-reading software etc., including alt text for diagrams+images (in the case of ‘F&N’, 552 pieces of alt text were required, some quite lengthy).
The new version is available (#OpenAccess as always) at: https://archive.org/details/cain_formandnumber_ebook_large
Feedback from users of screen readers would be very welcome!
Creating this version has been possible because of the ongoing LaTeX tagging project [https://latex3.github.io/tagging-project/] (thank you to the LaTeX team and other contributors!). I have been adapting my own #LuaLaTeX styles [https://codeberg.org/ajcain/minos] to use the new interfaces.
1/2
#accessibility #a11y #MathArt #HistMath #HistSci #MathematicalBeauty #aesthetics #typography #TeXLaTeX
-
Big update to ‘Form & Number: A History of Mathematical Beauty’: the PDFs are now *tagged* (plus various minor improvements).
A #TaggedPDF contains hidden extra semantic information to assist screen-reading software etc., including alt text for diagrams+images (in the case of ‘F&N’, 552 pieces of alt text were required, some quite lengthy).
The new version is available (#OpenAccess as always) at: https://archive.org/details/cain_formandnumber_ebook_large
Feedback from users of screen readers would be very welcome!
Creating this version has been possible because of the ongoing LaTeX tagging project [https://latex3.github.io/tagging-project/] (thank you to the LaTeX team and other contributors!). I have been adapting my own #LuaLaTeX styles [https://codeberg.org/ajcain/minos] to use the new interfaces.
1/2
#accessibility #a11y #MathArt #HistMath #HistSci #MathematicalBeauty #aesthetics #typography #TeXLaTeX
-
Another update to my #LuaLaTeX style "minos", used in ‘Form & Number: A History of Mathematical Beauty’ and my other books (links in profile).
Git repository: https://codeberg.org/ajcain/minos
Download documentation or source .zip/.tar.gz: https://codeberg.org/ajcain/minos/releases
Improvements mostly concern #TaggedPDF-related features:
- Sidenotes are now tagged as *notes* (same as footnotes), not as "Aside" (the default for marginal content).
- The theorem number appears in the proof heads even when \DocumentMetadata is used — in the previous version I had not integrated this feature into the new interfaces for theorem-like environments.
(The number also appears in the QED symbol, which is a long-standing feature I would like to highlight. I think is useful with nested proofs; example from docs attached.)
-
Another update to my #LuaLaTeX style "minos", used in ‘Form & Number: A History of Mathematical Beauty’ and my other books (links in profile).
Git repository: https://codeberg.org/ajcain/minos
Download documentation or source .zip/.tar.gz: https://codeberg.org/ajcain/minos/releases
Improvements mostly concern #TaggedPDF-related features:
- Sidenotes are now tagged as *notes* (same as footnotes), not as "Aside" (the default for marginal content).
- The theorem number appears in the proof heads even when \DocumentMetadata is used — in the previous version I had not integrated this feature into the new interfaces for theorem-like environments.
(The number also appears in the QED symbol, which is a long-standing feature I would like to highlight. I think is useful with nested proofs; example from docs attached.)
-
Another update to my #LuaLaTeX style "minos", used in ‘Form & Number: A History of Mathematical Beauty’ and my other books (links in profile).
Git repository: https://codeberg.org/ajcain/minos
Download documentation or source .zip/.tar.gz: https://codeberg.org/ajcain/minos/releases
Improvements mostly concern #TaggedPDF-related features:
- Sidenotes are now tagged as *notes* (same as footnotes), not as "Aside" (the default for marginal content).
- The theorem number appears in the proof heads even when \DocumentMetadata is used — in the previous version I had not integrated this feature into the new interfaces for theorem-like environments.
(The number also appears in the QED symbol, which is a long-standing feature I would like to highlight. I think is useful with nested proofs; example from docs attached.)
-
Géométrie hyperbolique dans (lua)latex avec le package luahyperbolic, Le jeudi 2 juillet 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/35463 #latex #lua #lualatex #géométrieHyperbolique #gutenberg #visioConférence
-
Géométrie hyperbolique dans (lua)latex avec le package luahyperbolic, Le jeudi 2 juillet 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/35463 #latex #lua #lualatex #géométrieHyperbolique #gutenberg #visioConférence
-
Géométrie hyperbolique dans (lua)latex avec le package luahyperbolic, Le jeudi 2 juillet 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/35463 #latex #lua #lualatex #géométrieHyperbolique #gutenberg #visioConférence
-
Géométrie hyperbolique dans (lua)latex avec le package luahyperbolic, Le jeudi 2 juillet 2026 de 20h00 à 21h00. https://www.agendadulibre.org/events/35463 #latex #lua #lualatex #géométrieHyperbolique #gutenberg #visioConférence
-
New version of my #LuaLaTeX style "minos".
Git repository: https://codeberg.org/ajcain/minos
Download documentation or source .zip/.tar.gz: https://codeberg.org/ajcain/minos/releases
- Many improvements related to creating #TaggedPDF, notably using template code for theorems and sectioning when \DocumentMetadata is used.
- Various new/adjusted/fixed kerning customizations.
-
New version of my #LuaLaTeX style "minos".
Git repository: https://codeberg.org/ajcain/minos
Download documentation or source .zip/.tar.gz: https://codeberg.org/ajcain/minos/releases
- Many improvements related to creating #TaggedPDF, notably using template code for theorems and sectioning when \DocumentMetadata is used.
- Various new/adjusted/fixed kerning customizations.
-
New version of my #LuaLaTeX style "minos".
Git repository: https://codeberg.org/ajcain/minos
Download documentation or source .zip/.tar.gz: https://codeberg.org/ajcain/minos/releases
- Many improvements related to creating #TaggedPDF, notably using template code for theorems and sectioning when \DocumentMetadata is used.
- Various new/adjusted/fixed kerning customizations.
-
New version of my #LuaLaTeX style "minos".
Git repository: https://codeberg.org/ajcain/minos
Download documentation or source .zip/.tar.gz: https://codeberg.org/ajcain/minos/releases
- Many improvements related to creating #TaggedPDF, notably using template code for theorems and sectioning when \DocumentMetadata is used.
- Various new/adjusted/fixed kerning customizations.
-
@yantar92 @jameshowell @11011110 @oantolin yes, we just got a thesis submitted with LuaLaTeX that passed the uni's accessibility tests. But I thought that the common wisdom was that this could not be achieved with beamer. If beamer now works that would be grand!
-
@yantar92 @jameshowell @11011110 @oantolin yes, we just got a thesis submitted with LuaLaTeX that passed the uni's accessibility tests. But I thought that the common wisdom was that this could not be achieved with beamer. If beamer now works that would be grand!
-
@yantar92 @jameshowell @11011110 @oantolin yes, we just got a thesis submitted with LuaLaTeX that passed the uni's accessibility tests. But I thought that the common wisdom was that this could not be achieved with beamer. If beamer now works that would be grand!
-
@yantar92 @jameshowell @11011110 @oantolin yes, we just got a thesis submitted with LuaLaTeX that passed the uni's accessibility tests. But I thought that the common wisdom was that this could not be achieved with beamer. If beamer now works that would be grand!
-
Vraiment c'est trop top #LaForgeEdu, #Tchap et #Mastodon. Mon petit projet de cours de #Biochimie en #LaTeX a pu être largement amélioré grâce à @louispaternault (passage sous #LuaLaTeX et implémentation de la génération PDF directement dans le GitLab de #LaForgeEdu) et @amelliug (modélisation de molécules en LaTeX avec #chemfig). Il n'y a vraiment que du bon qui ressort de ces interractions humaines. Vive les ressources pédagogiques libres 🥰 https://bio.forge.apps.education.fr/biomolecules/
-
Vraiment c'est trop top #LaForgeEdu, #Tchap et #Mastodon. Mon petit projet de cours de #Biochimie en #LaTeX a pu être largement amélioré grâce à @louispaternault (passage sous #LuaLaTeX et implémentation de la génération PDF directement dans le GitLab de #LaForgeEdu) et @amelliug (modélisation de molécules en LaTeX avec #chemfig). Il n'y a vraiment que du bon qui ressort de ces interractions humaines. Vive les ressources pédagogiques libres 🥰 https://bio.forge.apps.education.fr/biomolecules/
-
Vraiment c'est trop top #LaForgeEdu, #Tchap et #Mastodon. Mon petit projet de cours de #Biochimie en #LaTeX a pu être largement amélioré grâce à @louispaternault (passage sous #LuaLaTeX et implémentation de la génération PDF directement dans le GitLab de #LaForgeEdu) et @amelliug (modélisation de molécules en LaTeX avec #chemfig). Il n'y a vraiment que du bon qui ressort de ces interractions humaines. Vive les ressources pédagogiques libres 🥰 https://bio.forge.apps.education.fr/biomolecules/
-
Started applying my new #LuaLaTeX package "lua-simple-wrap" to the small-format version of ‘Form & Number: A History of Mathematical Beauty’.
Previously, various figures that were placed in the margin of the large format (using my package "marginalia" [https://ctan.org/pkg/marginalia]) were placed as normal figures in the small format, but they often looked awkwardly small (see 1st attached image). I have started using "lua-simple-wrap" to place many of them at the side of the page with the text wrapped around them (see 2nd attached image).
The advantage of "lua-simple-wrap" over other packages for wrapping text is that the code for each figure is placed at the same natural point in the paragraph as in the large-format version. This is important because the different versions are built from the same source by changing a global setting.
‘Form & Number’ (#OA as always): https://archive.org/details/cain_formandnumber_ebook_large (large format); https://archive.org/details/cain_formandnumber_ebook_small (small format)
"lua-simple-wrap" Git repository: https://codeberg.org/ajcain/lua-simple-wrap (still in development, not yet available on CTAN)
-
Started applying my new #LuaLaTeX package "lua-simple-wrap" to the small-format version of ‘Form & Number: A History of Mathematical Beauty’.
Previously, various figures that were placed in the margin of the large format (using my package "marginalia" [https://ctan.org/pkg/marginalia]) were placed as normal figures in the small format, but they often looked awkwardly small (see 1st attached image). I have started using "lua-simple-wrap" to place many of them at the side of the page with the text wrapped around them (see 2nd attached image).
The advantage of "lua-simple-wrap" over other packages for wrapping text is that the code for each figure is placed at the same natural point in the paragraph as in the large-format version. This is important because the different versions are built from the same source by changing a global setting.
‘Form & Number’ (#OA as always): https://archive.org/details/cain_formandnumber_ebook_large (large format); https://archive.org/details/cain_formandnumber_ebook_small (small format)
"lua-simple-wrap" Git repository: https://codeberg.org/ajcain/lua-simple-wrap (still in development, not yet available on CTAN)
-
Started applying my new #LuaLaTeX package "lua-simple-wrap" to the small-format version of ‘Form & Number: A History of Mathematical Beauty’.
Previously, various figures that were placed in the margin of the large format (using my package "marginalia" [https://ctan.org/pkg/marginalia]) were placed as normal figures in the small format, but they often looked awkwardly small (see 1st attached image). I have started using "lua-simple-wrap" to place many of them at the side of the page with the text wrapped around them (see 2nd attached image).
The advantage of "lua-simple-wrap" over other packages for wrapping text is that the code for each figure is placed at the same natural point in the paragraph as in the large-format version. This is important because the different versions are built from the same source by changing a global setting.
‘Form & Number’ (#OA as always): https://archive.org/details/cain_formandnumber_ebook_large (large format); https://archive.org/details/cain_formandnumber_ebook_small (small format)
"lua-simple-wrap" Git repository: https://codeberg.org/ajcain/lua-simple-wrap (still in development, not yet available on CTAN)
-
Started applying my new #LuaLaTeX package "lua-simple-wrap" to the small-format version of ‘Form & Number: A History of Mathematical Beauty’.
Previously, various figures that were placed in the margin of the large format (using my package "marginalia" [https://ctan.org/pkg/marginalia]) were placed as normal figures in the small format, but they often looked awkwardly small (see 1st attached image). I have started using "lua-simple-wrap" to place many of them at the side of the page with the text wrapped around them (see 2nd attached image).
The advantage of "lua-simple-wrap" over other packages for wrapping text is that the code for each figure is placed at the same natural point in the paragraph as in the large-format version. This is important because the different versions are built from the same source by changing a global setting.
‘Form & Number’ (#OA as always): https://archive.org/details/cain_formandnumber_ebook_large (large format); https://archive.org/details/cain_formandnumber_ebook_small (small format)
"lua-simple-wrap" Git repository: https://codeberg.org/ajcain/lua-simple-wrap (still in development, not yet available on CTAN)
-
I've just published my first LaTeX package!
Countwords is a simple package for counting words in LaTeX documents. Words are counted into a standard LaTeX counter, which can then printed (or otherwise manipulated) in all the normal ways. You can stop and counting whenever you want, and have multiple independent counters.
It's on CTAN here: https://ctan.org/pkg/countwords
P.S. credit to Philipp Gesang @phgsng for the original lua wordcount code.
-
I've just published my first LaTeX package!
Countwords is a simple package for counting words in LaTeX documents. Words are counted into a standard LaTeX counter, which can then printed (or otherwise manipulated) in all the normal ways. You can stop and counting whenever you want, and have multiple independent counters.
It's on CTAN here: https://ctan.org/pkg/countwords
P.S. credit to Philipp Gesang @phgsng for the original lua wordcount code.
-
I've just published my first LaTeX package!
Countwords is a simple package for counting words in LaTeX documents. Words are counted into a standard LaTeX counter, which can then printed (or otherwise manipulated) in all the normal ways. You can stop and counting whenever you want, and have multiple independent counters.
It's on CTAN here: https://ctan.org/pkg/countwords
P.S. credit to Philipp Gesang @phgsng for the original lua wordcount code.
-
I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.
I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.
#Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex
-
I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.
I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.
#Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex
-
I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.
I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.
#Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex
-
I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.
I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.
#Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex
-
My new #LuaLaTeX package: lua-simple-wrap
This package allows easy wrapping of text around small figures, pull quotes, etc. (See attached image.)
Unlike (I think) all other LaTeX packages for wrapping text around things, the wrapped object can be specified at its natural place in the text, and the package works out where it should appear. Virtually all the processing happens on the Lua side.
The package is semi-experimental, and definitely requires more work before I submit it to CTAN, but the basic functionality is in place and seems to be working well. In particular, tagging support (for producing accessible PDFs) is already present.
Git repository: https://codeberg.org/ajcain/lua-simple-wrap
Download documentation and built package: https://codeberg.org/ajcain/lua-simple-wrap/releases
If you try it, feedback would be much appreciated!
-
My new #LuaLaTeX package: lua-simple-wrap
This package allows easy wrapping of text around small figures, pull quotes, etc. (See attached image.)
Unlike (I think) all other LaTeX packages for wrapping text around things, the wrapped object can be specified at its natural place in the text, and the package works out where it should appear. Virtually all the processing happens on the Lua side.
The package is semi-experimental, and definitely requires more work before I submit it to CTAN, but the basic functionality is in place and seems to be working well. In particular, tagging support (for producing accessible PDFs) is already present.
Git repository: https://codeberg.org/ajcain/lua-simple-wrap
Download documentation and built package: https://codeberg.org/ajcain/lua-simple-wrap/releases
If you try it, feedback would be much appreciated!
-
My new #LuaLaTeX package: lua-simple-wrap
This package allows easy wrapping of text around small figures, pull quotes, etc. (See attached image.)
Unlike (I think) all other LaTeX packages for wrapping text around things, the wrapped object can be specified at its natural place in the text, and the package works out where it should appear. Virtually all the processing happens on the Lua side.
The package is semi-experimental, and definitely requires more work before I submit it to CTAN, but the basic functionality is in place and seems to be working well. In particular, tagging support (for producing accessible PDFs) is already present.
Git repository: https://codeberg.org/ajcain/lua-simple-wrap
Download documentation and built package: https://codeberg.org/ajcain/lua-simple-wrap/releases
If you try it, feedback would be much appreciated!
