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

The jplain class content frame is not related to the page #1402

Open
alerque opened this issue May 26, 2022 · 4 comments
Open

The jplain class content frame is not related to the page #1402

alerque opened this issue May 26, 2022 · 4 comments
Labels
bug Software bug issue
Milestone

Comments

@alerque
Copy link
Member

alerque commented May 26, 2022

The jplain class has a hard coded content frame size that works on A4 paper, but changing the papersize only changes the PDF canvas but not the content frame... Usually resulting in the content being outside of the page.

It should be fixed to have a content frame that calculates it's properties based on the page frame including a sensible grid for hanmen content.

@alerque alerque added the bug Software bug issue label May 26, 2022
@alerque alerque added this to the v0.13.x milestone May 26, 2022
@ctrlcctrlv
Copy link
Member

So that's why that happens…

@alerque alerque modified the milestones: v0.13.x, v0.14.x Jun 24, 2022
@alerque
Copy link
Member Author

alerque commented Nov 18, 2022

Hey @ctrlcctrlv can you give me a yes/no sanity check here? I don't do kihonhanmen or any other CJK / tate stuff so I'm shooting in the dark here, but...

The current hanmenkuyoshi package wants a frame with two starting edges (currently top & left but even if we make no other changes making this top & right would avoid the blank page problem), a grid size and a row/column count. This seems like a clumsy way to specify a size because it does not automatically adjust for the paper size at all and making it do so is a multi-step process.

Would it make any sense to instead expect a frame spec with all 4 boundaries already specified and then ask for just the grid size? Then we could automatically calculate the row/column count quite easily and just fill out the frame.

@ctrlcctrlv
Copy link
Member

ctrlcctrlv commented Nov 18, 2022

@alerque I think it's very clumsy how it works and that's why I avoid SILE's tate implementation :-(

We shouldn't be asking the user to figure out the grid size at all. We should figure it out based on the body text font size. The size of the 基本版面 (kihonhanmen; main text area) should be determined from the size of one 全角 (zenkaku; full-width character) and the measurements of the page (紙の寸法; kami no sunpō), entirely automatically.

@ctrlcctrlv
Copy link
Member

The implementation of 縦書き (tategaki; vertical typesetting) that I use for Japanese is entirely automatic, upLaTeX. I also have experimented with LuaTeX-ja, and it is also automatic. I would really like to use SILE for this, but @simoncozens called his 版面 (hanmen; (Japanese) printed page) implementation 反面教師 (hanmen kyōshi) for a reason: in Japanese this 四字熟語 (yoji-jukugo; four character idiom) means "a good example of what not to do". And it really, really is that. I think he meant it to be temporary but then got busy with other stuff and it became semi-permanent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Software bug issue
Projects
Status: No status
Development

No branches or pull requests

2 participants