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.

* an
* unordered
* list

1. an
1. ordered
1. list

> 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:

* an
* unordered
* list

1. an
1. ordered
1. list

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

But wait, there's more!

|this|is|
|-|-|
|a|table|

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!

https://kildor.name/react/inat-converter/Met Google translate kun je ook statistisch journaal posts maken. er is een tool voor die de noodzakelijke alineas (page breaks) toevoegt, origineel is het gebruikt om statische to Flora of Russia projectte schrijven en zet ook wat statistieken om in HTML .

There are several tabs (Species, experts, observers) in the project. You can copy the text, for example
Ранг Пользователь Наблюдения Вид
1 apseregin 28 578 1 793
2 dni_catipo 16 286 949
3 panasenkonn 15 417 1 084
4 velibortravoved 12 613 691
5 melodi_96 11 083 950
and paste it to the script. It converts the plain text with tabs to the table for better reading,
iNat strips the table tags from comments, so I can't show you the result. The markup will be like this:

Publicado el 07 de noviembre de 2020 a las 10:13 PM por ahospers