Comments (4)
Why not providing this as a by default not enabled feature, that could be enabled just with a single command?
That is not impossible to consider, certainly more changes have been made in recent years than in earlier periods but it would mean adding \if@wibble....\fi
in several places in the toc code, and the question is how many of
https://ctan.org/topic/toc-etc
patch at that point and would give errors or fail to work as intended if the patch failed....
That said, there need to be changes in that area to support pdf tagging, so if such a feature is going to be considered , adding it at the same time might be a possibility.
Note this isn't closed as not planned it's labeled as long term enhancement, whether that makes a difference in practice we'll see....
from latex2e.
But compatibility is not the only issue here. Just taking the maximum is in my experience seldom a good a idea, e.g. TLC3 would have looked rather bad this way and it had a bunch of such issues as well. For example, 10.10.10 which would have made the whole TOC look really ugly if everything would have been based on this. Or the LOT where we have 10.100 that has 5 digits plus a period while most entries have 2 or maximum of 3 digits. So basing everything on xx.xxx would be rather bad.
So basically what I'm saying is that yes there is something that should be offered but in many cases the simple maximum is not good enough for a quality result and instead you need to handtune the exceptions if they are few.
from latex2e.
You mean in case you spend 30 years enlarging source2e.tex
and accidentally go over a thousand pages:-)
This has long been known as a common issue with larger documents (or documents with unusual page formatting) It wouldn't be particularly difficult to keep track of the width and store the maximum (or less computationally expensive just keep track of the largest page (and section) number and assume the typeset version is monotonically increasing in width) you could then write them to the aux and use the widths on the next run.
The problem (as always) is compatibility: it's not clear this can easily be added to the standard classes without impacting the many packages that modify the table of contents layout.
It's certainly a feature that could be considered for any new classes though.
from latex2e.
You mean in case you spend 30 years enlarging
source2e.tex
and accidentally go over a thousand pages:-)
You read my mind! 😉
This has long been known as a common issue with larger documents (or documents with unusual page formatting) It wouldn't be particularly difficult to keep track of the width and store the maximum (or less computationally expensive just keep track of the largest page (and section) number and assume the typeset version is monotonically increasing in width) you could then write them to the aux and use the widths on the next run.
👍
The problem (as always) is compatibility: it's not clear this can easily be added to the standard classes without impacting the many packages that modify the table of contents layout.
Sigh...
It's certainly a feature that could be considered for any new classes though.
Why not providing this as a by default not enabled feature, that could be enabled just with a single command?
from latex2e.
Related Issues (20)
- \DeclareDefaultHookRule does not work HOT 11
- upquote package has no effect on macrocode environments HOT 2
- lthooks doc ActivateGenericHook HOT 4
- Undocumented limitation on builtin generic hook names HOT 3
- ltkeys: Global options starting surrounded by spaces in the input are not removed from the unused option list HOT 3
- Many warnings about reguler to m series substitution as corollary from loading main font using regular not m in its font definition file HOT 4
- fntguide: No redefinition information in the transcript file HOT 3
- `\AddToHook` broken in old lthooks release for undeclared hooks
- \verbatiminput* from the verbatim package vs TABs HOT 2
- Bad filehook-bug-140.lvt HOT 1
- Package textcomp Info: Symbol ... not provided by HOT 9
- Conditional statements syntax HOT 5
- `\dots` not working correctly with `\cong` HOT 4
- minor doc tweaks to ltfilehook HOT 2
- source2e documentation footers/ \ProvidesFile of base .dtx HOT 3
- Possible source2e improvements HOT 3
- Image upscaled for no apparent reason HOT 7
- Avoid option conflicts between classs and packages HOT 4
- Test more packages before publishing a new release HOT 14
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from latex2e.