Closing old issues before convertion.#5704
Conversation
|
This allowed the erasing of |
| translate = "remove"> | ||
|
|
||
| <!-- Erased in 2026-06, long time empty --> | ||
| <!-- Erased in 2024-08, doc-ru --> |
There was a problem hiding this comment.
As this file will get longer should we have a convention for adding lines? This should also make it easier for other contributors to phase out entities.
Perhaps something like:
<!-- Erased in <date>, ref: #3633, todo: doc-<lang>, doc-<lang> -->
<!-- Erased in <date>, ref: */bookinfo.xml, todo: doc-<lang> -->
There was a problem hiding this comment.
These conventions are good, and please add them to new entries.
But as this file may grow and be rarely trimmed, or have its comments updated, I think the only real way this file will be reduced is with bruteforce testing its contents against all languages, from time to time.
I was working in an "exact" userland XML assembler that could be used instead, but as it is constantly sidestepped, and my time in docs grows thin, I can only think in the bruteforce alternative for the future, where exact or updated comments may have low impact in the end.
kamil-tekiela
left a comment
kamil-tekiela
left a comment
There was a problem hiding this comment.
Why wait until August? You can merge it now.
|
At first I worried this would conflict with manual split (and so, August). But nothing clashed, I will merge it later today. |
3 participants
Move some long erased entities into entities.remove.ent, so issues can be closed and empty files deleted.
Plan to merge this in early August.