We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Spaces for mailto links must be formatted with the escape code %20, including after the colon. This is in accordance with the commonmark spec (CommonMark Spec: Link Destination)
%20
Examples:
In tinkr:
mailto with no space works:
tinkr::yarn$new(textConnection("[link](mailto:zkamvar@example.com)\n"))$body |> xml2::xml_child() |> as.character() |> writeLines() #> <paragraph> #> <link destination="mailto:zkamvar@example.com" title=""> #> <text xml:space="preserve">link</text> #> </link> #> </paragraph>
mailto with a space converts it to text with an internal mailto link (since the email is automatically converted)
tinkr::yarn$new(textConnection("[link](mailto: zkamvar@example.com)\n"))$body |> xml2::xml_child() |> as.character() |> writeLines() #> <paragraph> #> <text xml:space="preserve">[link](mailto: </text> #> <link destination="mailto:zkamvar@example.com" title=""> #> <text xml:space="preserve">zkamvar@example.com</text> #> </link> #> <text xml:space="preserve">)</text> #> </paragraph>
Created on 2022-05-11 by the reprex package (v2.0.1)
The text was updated successfully, but these errors were encountered:
I am leaving this here just in case anyone else runs into this issue and wants to know the fix.
Sorry, something went wrong.
No branches or pull requests
Spaces for mailto links must be formatted with the escape code
%20
, including after the colon. This is in accordance with the commonmark spec (CommonMark Spec: Link Destination)Examples:
In tinkr:
mailto with no space works:
mailto with a space converts it to text with an internal mailto link (since the email is automatically converted)
Created on 2022-05-11 by the reprex package (v2.0.1)
The text was updated successfully, but these errors were encountered: