Skip to content

Conversation

@ylemkimon
Copy link
Member

  • Remove empty lower right cells, where appropriate
  • Escape backticks using <code></code>
  • Escape vertical bars(|) using <code> and HTML entity code
  • Normalize documentation links
  • Add plugin to remove empty theads

@ylemkimon ylemkimon requested a review from ronkok July 28, 2018 00:06
@codecov
Copy link

codecov bot commented Jul 28, 2018

Codecov Report

Merging #1511 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #1511   +/-   ##
======================================
  Coverage    84.1%   84.1%           
======================================
  Files          79      79           
  Lines        4561    4561           
  Branches      804     804           
======================================
  Hits         3836    3836           
  Misses        630     630           
  Partials       95      95

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8a38035...62dc55e. Read the comment docs.

Copy link
Collaborator

@ronkok ronkok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ylemkimon Thank you for this work. It significantly upgrades the page and I see nothing here that I wish to change.

There are some remaining issues and if you know ways to fix them, please feel free to do so. The issues:

  1. \not is not working properly. I suspect that is because the CSS and JS of this page are not in sync.
  2. There is excess padding in the environment table.
  3. Nested $ delimiters do not work
  4. The "|" character cannot be used inside a table, which makes it impossible to demonstrate the {c|c} argument to the {array} environment.

@ronkok ronkok merged commit 4114288 into KaTeX:master Jul 28, 2018
@ylemkimon
Copy link
Member Author

ylemkimon commented Jul 28, 2018

@ronkok Thank you for the review! The excessive padding is because the table is vertically aligned by the baseline, vertical-align: baseline;. I'm not sure what is the best vertical-align for tables, though.

@ylemkimon ylemkimon deleted the supported branch July 28, 2018 01:25
@@ -0,0 +1,30 @@
module.exports = function(md, options) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a top-level comment to this file explain its purpose.

|:---------------------|:---------------------|:---------------------|:-----
|$\text{\'{a}}$ `\'{a}`|$\text{\~{a}}$ `\~{a}`|$\text{\.{a}}$ `\.{a}`|$\text{\H{a}}$ `\H{a}`
|$\text{\`{a}}$ `\`{a}`|$\text{\={a}}$ `\={a}`|$\text{\"{a}}$ `\"{a}`|$\text{\v{a}}$ `\v{a}`
|$\text{\`{a}}$ <code>\\`{a}</code>|$\text{\={a}}$ `\={a}`|$\text{\"{a}}$ `\"{a}`|$\text{\v{a}}$ `\v{a}`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the double backslash necessary here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kevinbarabash It seems so.

|$[ ]$ `[ ]` |$\lbrack~\rbrack$ `\lbrack`<br>$~~~~$`\rbrack`|$⌊~⌋$ `⌊ ⌋`|$\lfloor~\rfloor$ `\lfloor`<br>$~~~~$`\rfloor` |$\downarrow$ `\downarrow`
|$\{ \}$ `\{ \}`|$\lbrace \rbrace$ `\lbrace`<br>$~~~~$`\rbrace`|$⎰⎱$ `⎰⎱` |$\lmoustache \rmoustache$ `\lmoustache`<br>$~~~~$`\rmoustache`|$\updownarrow$ `\updownarrow`
|$⟨~⟩$ `⟨ ⟩` |$\langle~\rangle$ `\langle`<br>$~~~~$`\rangle`|$⟮~⟯$ `⟮ ⟯`|$\lgroup~\rgroup$ `\lgroup`<br>`\rgroup` |$\Uparrow$ `\Uparrow`
|$\vert$ $\colorbox{#f3f3f4}{\textbar}$ |$\vert$ `\vert` |$┌ ┐$ `┌ ┐`|$\ulcorner \urcorner$ `\ulcorner`<br>$~~~~$`\urcorner` |$\Downarrow$ `\Downarrow`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why were we using \colorbox before?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kevinbarabash I was unable to use the | character inside a table. Even when inside backticks, the Remarkable parser treated the character as a cell separator. The \colorbox was my attempt to simulate the appearance of a code string, since in it I could use \textbar.

@ylemkimon's use of <code> tags is much better.

|$\in$ `\in` |$\mid$ `\mid` |$\to$ `\to`|$\implies$ `\implies`
|$\notin$ `\notin` |$\land$ `\land`|$\gets$ `\gets` |$\impliedby$ `\impliedby`
|$\ni$ `\ni` |$\lor$ `\lor` |$\leftrightarrow$ `\leftrightarrow`|$\iff$ `\iff`
|$\notni$ `\notni` || |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for cleaning up these stray |. We should maybe look at adding a linter for our markdown to catch these things.

|$~$ | `\providecommand\macroname[numargs]{definition}`

Macros can also be defined in the KaTeX [rendering options](./options).
Macros can also be defined in the KaTeX [rendering options](options.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call on making all links use .md.

@ylemkimon ylemkimon mentioned this pull request Jul 28, 2018
@edemaine
Copy link
Member

@ronkok Maybe you could open a new issue with those points, so it's easier to track them.

@ronkok
Copy link
Collaborator

ronkok commented Jul 28, 2018

@edemaine I've added three of the issues to the list in #1505. The fourth issue was already implicitly there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants