-
Notifications
You must be signed in to change notification settings - Fork 800
Mark up unspecific constants as replaceable #1963
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
Conversation
Great idea of @Girgias, in my opinion.
33d0a76
to
fdb651c
Compare
Does our DTD really not allow Otherwise, LGTM, but I would wait a bit before merging to not put too much strain on translation before the release of 8.2. |
Now that I think about it, having the replaceable tag be just after the constant one will probably help if (one can dream) we get links to constants automatically generated as those will need to be ignored |
Yeah, I got a failure when running
Indeed, avoinding mixed content in |
My preference would be to only mark up the replaceable part as I don't buy the argument that Regardless, either way is an improvement on what we have now.
What was the failure? A quick search/replace to the |
I've tried again, and indeed it works. I must have messed something up in my first attempt.
Well, there isn't probably much of a difference, so I'm pushing a commit where only the |
This has at least partially been done already, so I'm closing this PR. |
Great idea of @Girgias, in my opinion.