Find consistent way to refer to vertical mirroring

Open
#108 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
content

Research direction

Start by reviewing the existing .rev and .inv naming conventions described in the issue, then compare the proposed alternatives for vertical mirroring and 180-degree rotation. Done requires an agreed naming convention and a clear decision on how the affected symbols, including the obtuse-angle variants, should be named.

Written by the indexing model from the issue text.

Description

meta

We seem to only have two current conventions:

.rev - Horizontal mirroring
.inv - Rotate by 180 degrees

These can also be combined to yield

.rev.inv- Vertical mirroring

There are several drawbacks with the current situation:

  • The word "invert" can also imply vertical mirroring. In fact, this is the sense in which it is used in unicode naming (though inconsistently), with "turned" used for rotation by 180 degres.
  • If there is only a vertically mirrored variant, then using .rev.inv isn't exactly the most natural modifier. This is the case for obtuse angles, where ⦦ (currently angle.oblique) and ⦧ (not currently named) are the only variants.
  • Even when there are other variants, it would still be beneficial to have a single modifier for vertical mirroring for semantic purposes.

I see several possibilities

  • Introduce .turned, .flip or .rot (though this has also been proposed for 90 degrees) for rotation by 180 degrees, and use .inv for vertical mirroring
  • Keep .inv for rotation by 180 degrees, and use .flip for vertical mirroring
  • Something like .rev.h and .rev.v (though I can imagine this leading to conflicts if we don't have #94 #95 )
Dominant language
Rust
Stars
53
Forks
22
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 typst/codex

All issues in typst/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.