tul/tultemplate2
3
1
Fork 0
Code Issues 5 Releases 5 Activity

Adhere to consultation remarks #12

New Issue
Open
opened 2025-10-08 10:40:57 +00:00 by ondrej.mekina · 4 comments
ondrej.mekina commented 2025-10-08 10:40:57 +00:00
Owner
Copy Link
  • Source the first four pages from external file (this should be generated by STAG)
  • Change citations to be (always - no matter the locale) square brackets instead of paretheses
  • Add square brackets to bibliography numbers instead of dots
  • Add remark about underlines - they should not be used
- [ ] Source the first four pages from external file (this should be generated by STAG) - [ ] Change citations to be (always - no matter the locale) square brackets instead of paretheses - [ ] Add square brackets to bibliography numbers instead of dots - [ ] Add remark about underlines - they should not be used
ondrej.mekina added the
enhancement
breaking_api
 labels 2025-10-08 10:40:57 +00:00
ondrej.mekina self-assigned this 2025-10-08 10:40:57 +00:00
matej.zucha was assigned by ondrej.mekina 2025-10-08 10:40:57 +00:00
michal.prochazka commented 2025-10-09 12:42:16 +00:00
Owner
Copy Link

Also, single-character words should not be at the end of the line.

Also, single-character words should not be at the end of the line.
michal.prochazka commented 2025-10-09 12:46:26 +00:00
Owner
Copy Link

Also, we have verified that 2-way real-time collaboration works without the need for Typst Pro.

Also, we have verified that 2-way real-time collaboration works without the need for Typst Pro.
👍 1
ondrej.mekina commented 2025-10-09 13:31:03 +00:00
Author
Owner
Copy Link

This seems poorly worded and must be further consulted. That's why it isn't in the original issue's tasks.

Also... "single-character words" seems like a big oversimplification. We could do that. However that is not the actual case.

See https://prirucka.ujc.cas.cz/?id=880

It's important to note that even UJC states that this is an advice rather than a rule. I could not find any relevant rector's decree on TUL's website.

The implementation is likely to be extremely difficult as we might need to include a comprehensive list of unbreakable terms.

The template already penalizes leaving a single character word at the end of a line, but it does not completely forbid it (if, for example, breaking before would lead to larger-than-allowed interword spacing).

I'm going to get another opinion on this and open another issue (if needed). For now, this is more of a "nice to have" than a critical feature.

This seems poorly worded and must be further consulted. That's why it isn't in the original issue's tasks. Also... "single-character words" seems like a big oversimplification. We could do _that_. However that is not the actual case. See https://prirucka.ujc.cas.cz/?id=880 It's important to note that even UJC states that this is an advice rather than a rule. I could not find any relevant rector's decree on TUL's website. The implementation is likely to be extremely difficult as we might need to include a comprehensive list of unbreakable terms. The template _already penalizes_ leaving a single character word at the end of a line, but it does not completely forbid it (if, for example, breaking before would lead to larger-than-allowed interword spacing). I'm going to get another opinion on this and open another issue (if needed). For now, this is more of a "nice to have" than a critical feature.
ondrej.mekina commented 2025-10-09 13:40:21 +00:00
Author
Owner
Copy Link

We should fix this in example documents tho.

We should fix this in example documents tho.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
breaking_api
A breaking change in the API exposed to the user (usually an argument removal, renaming or a new required argument)
bug
Unexpected or inconsistent behavior
docs
Documentation improvement or change
enhancement
A task/feature that should be done later
No Label
breaking_api
enhancement
Milestone
No items
No Milestone
Assignees
Clear assignees
matej.zucha michal.prochazka ondrej.mekina
No Assignees ondrej.mekina matej.zucha
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: tul/tultemplate2#12
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?