26.Verrijking text met Opmaak, Mark-Up languages met CONTROL toets

De opmaak voor een MARK UP tekst is sinds de zomer van 2020 verrijkt en omdat ik deze post gemist had heb ik het even bij mijn eigen journaal toegevoegd. Je kunt nu dmv de CONTROL toets de taal verrijken. Markdown uitgebreid naar de comments en de ID velden.in comments and IDs and the formatting buttons. Mocht je niet bekend zijn met de MARKUP language, het is sterk verwant aan het gewone HTML en je kunt nu gewoon toetsencombinatens gebruiken in de add comments and IDs op de iNaturalist.org website om te kijken hoe deze opmaak nu precies werkt.

Code Output Keyboard Shortcut
*italic* italic CMD-i / CTRL-i
**bold** bold CMD-b / CTRL-b
[link](https://www.inaturalist.org) link CMD-k / CTRL-k
* an
* unordered
* list
  • an
  • unordered
  • list
1. an
1. ordered
1. list
  1. an
  2. unordered
  3. list

> block quoted text is a nice way
>
> to quote external sources
        
block quoted text is a nice way

to quote external sources
New support for Markdown in comments and IDs and the formatting buttons.For those not familiar with Markdown, it's a more convenient formatting scheme than HTML that builds on how you may already express things like emphasis in plain text. You can use the buttons that now display when you add comments and IDs on the website to see how this formatting works, but here's on overview:
Code Output Keyboard Shortcut
*italic* italic CMD-i / CTRL-i
**bold** bold CMD-b / CTRL-b
[link](https://www.inaturalist.org) link CMD-k / CTRL-k
* an
* unordered
* list
  • an
  • unordered
  • list
1. an
1. ordered
1. list
  1. an
  2. unordered
  3. list

> block quoted text is a nice way
>
> to quote external sources
        
block quoted text is a nice way

to quote external sources

But wait, there's more!

Code Output
`code` code
|this|is|
|-|-|
|a|table|
this is
a table

The important bit is the row of hyphens below the header row.

We're supporting most of basic Markdown formatting, plus the tables extension, even though we don't have buttons for all those things.

It's also worth noting that we're supporting Markdown on comments, identifications, journal posts, and mostly on user profiles and project descriptions (you may run into trouble if that text is being truncated as it is on the project detail page). We're also supporting Markdown in the mobile apps for comments and IDs right now, even though we don't have the formatting buttons there. Mobile support for Markdown in user profiles, project descriptions, and journal posts is a work in progress (bold, italic, and links work fine, lists and tables not quite). We're still supporting HTML like we used to, but we're parsing it a bit more striclty than we used to. There are also a few weird cases where past text may now be formatted incorrectly, e.g. if you (like me) were in the habit of listing traces through keys like this,

1. Hairy patella
4. Red tail
18. Falcate toes

you'll need to switch to something like

1\. Hairy patella
4\. Red tail
18\. Falcate toes

Finally, thanks to everyone who chimed in on the Forum about this. Also, huge kudos to todtb for contributing the keyboard shortcuts for the text editor and for adding it to Identify (he's also working on making the text editor available when editing comments and identification remarks). He just volunteered to do both and did a great job, so thank you!

26.Verrijking text met Opmaak, Mark-Up languages met CONTROL toets
Publicado por ahospers ahospers, 08 de noviembre de 2020

Comentarios

Thumb

HTML is still supported but only a few tags are allowed. is not allowed as it seems but you can use for the same effect. Or you could use Markdown which is also supported as explained in this post:
https://www.inaturalist.org/posts/38475-less-agreeable-observations-more-agreeable-text-formatting 2
The markdown for italics would be text in italics.
It ain’t necessarily so. It depends on whether the text is being read by a visual browser, a screen reader or other agent (such as a search engine).

https://stackoverflow.com/questions/271743/whats-the-difference-between-b-and-strong-i-and-em
Alright then, for screen readers is better defined. So it is actually preferable. Otherwise they should be rendered the same.
Since when is it no longer allowed? It worked just fine until recently and it’s still listed as acceptable text formatting code here: https://forum.inaturalist.org/t/useful-html-tags-for-inaturalist-comments-and-other-text-wiki/6198

Actually, not quite right. In markdown, the asterisk is used to delimit “emphasis” NOT “italics”, so it is equivalent to html . This may be getting a bit pedantic, but is not guaranteed to render as italics (although it usually does). When we are writing comments with latin binomials, those really should be rendered as italics, not just emphasis, so the tag is more appropriate than the markdown asterisk. (That said, I have started using the markdown * in my comments, just because it’s easier.)

Publicado por ahospers hace alrededor de 2 meses (Marca)

Agregar un comentario

Acceder o Crear una cuenta para agregar comentarios.