Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Figure out how diagrams should work

Open
#141 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
latex, tex
Domain
documentation

Research direction

Start with the existing Illustrator-to-TikZ workflow described in the issue, including Inkscape, Poppler import, svg2tikz, tikzscale, and open-logic.sty. Review the wiki and the wrapfig limitation, then define a diagram style, decide how scaling should work, and identify where sources and scripts should live.

Written by the indexing model from the issue text.

Description

For issue #119 @pdaniell contributed Illustrator files. I converted them to Tikz via Inkscape (Poppler import, svg2tikz export) and then ran a script to convert the color names to ones that are now defined in open-logic.sty. tikzscale makes the images the right size, but does not scale line widths so if someone provides an AI or even an Inkscape file with different line widths from those first ones they will look different and possibly not good at all.

  • Need to define a diagram style in the wiki
  • Figure out if tikzscale is the best way to scale diagrams
  • Put the sources and scripts in a separate repository
  • wrapfig down't seem to work next to theorem environments, so having figures be only half the line width and text wrap around doesn't work (it's ok in the biographies since the photos show up next to regular paragraph text)
Dominant language
TeX
Stars
1.4k
Forks
289
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLogicProject/OpenLogic

All issues in OpenLogicProject/OpenLogic

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.