Skip to content
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

Inconsistent list indentation depending on marker width #4126

Open
1 task done
Gravitonic opened this issue May 13, 2024 · 0 comments
Open
1 task done

Inconsistent list indentation depending on marker width #4126

Gravitonic opened this issue May 13, 2024 · 0 comments
Labels
bug Something isn't working layout Related to layout, positioning, etc.

Comments

@Gravitonic
Copy link

Description

Because the layout of lists (list and enum) are adjusted by the spacing before and after markers, the width of the marker itself can affect the indentation of the list. Since different lists' markers can have different widths, this means that lists can have different indentation:

Screenshot

Untitled

Typst code to reproduce

+ one
+ two
+ three

intervening paragraph

11. eleven
+ twelve
+ thirteen

In contrast, LaTeX, Google Docs, and Microsoft Word all seem to let users set the indentation based on the list item bodies.

LaTeX

Screenshot 2024-05-13 at 9 32 14 AM

Google Docs

image

Microsoft Word

image

Reproduction URL

https://typst.app/project/rqnPOljOs8eDzgh36DKpki

Operating system

Web app, macOS

Typst version

  • I am using the latest version of Typst
@Gravitonic Gravitonic added the bug Something isn't working label May 13, 2024
@Gravitonic Gravitonic changed the title Write a short and descriptive title! Inconsistent list indentation depending on marker width May 13, 2024
@Enivex Enivex added the layout Related to layout, positioning, etc. label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working layout Related to layout, positioning, etc.
Projects
None yet
Development

No branches or pull requests

2 participants