-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 <tt>
tag is obsolete
#127
Conversation
You want to replace that with |
At any rate, shouldn't the pre tag be doing the monospacing? See issue #128 |
I think The example showed that results are different from without tt/code and tt/code. You are right, the |
The fact that it was intended for formatting is exactly the reason it became obsolete. Formatting is the job of CSS. I see no difference in the formatting of those three (the spacing is different between the |
I agree with you that Since I am not a designer, I think you want to send the CSS fix for formatting and the monospace font for #128. |
As I mentioned in #128, I don't understand the directory structure, and can't find any CSS files to edit. |
Looking at the code, it appears that the asciidoc parser just uses |
My initial goal was to output (nearly) the same HTML that the asciidoc command did, and they indeed still output tt tags. That said, in gitscm-next that's done by our own templates and not our Asciidoc parser, so we do have some freedom to make it look the way we like. I wouldn't want us to drift too far from the official HTML docs, but this seems safe to me. |
skeleton for catalan translation
Closing as stale (the template in question isn't used anymore; we just output whatever asciidoctor says). |
If these templates are no longer used, should they not be deleted from |
They are, aren't they? |
My mistake, confused my fork with upstream |
At least, according to https://developer.mozilla.org/en/HTML/Element/tt