Ordered lists with non-number markers

Request: Add “type” attribute of <ol> to whitelist. Suggestion to do the same with “reversed” for <ol>, and “value” for <li>, for similar but less common reasons.

Purpose: These attributes are intended for use where the marker of ordered list items itself conveys meaning to the content of the list. Typically this is the case when list items are intended to be referred to via this marker. This is in contrast to CSS list-style-type which is intended where the choice of marker carries no significant purpose. (Though I did see it recommended for forum-wide localization, which is pretty great!)

Background: While attempting to quote an official reference document, I discovered an apparent limitation in list formatting which prevents doing so accurately. Quite often, list markers are purely stylistic. However, they are occasionally used to facilitate reference in list-heavy documents. For example, in official and legal documents, a list item (or sub-item) might be referred to by list marker: “Official Document Article I, section 1(a)(i)”

For Markdown, there’s no mention in the CommonMark specification, and indeed it specifies only digits, 0-9. But while most interpreters don’t permit letters for lists(including markdown-it), a couple do:

I’m uncertain of whether a standard method is available in BBCode, to the extent anything is standard in BBCode. I was unable to find anything more advanced than starting at an arbitrary digit. BBCode list tags don’t appear used by Discourse, anyway.

With HTML and HTML+style, neither produce the correct result:

3 Me gusta

Looking at GitHub, implementing this would likely be simply a matter of adding them to this list:
https://github.com/discourse/discourse/blob/master/app/assets/javascripts/pretty-text/white-lister.js#L181-L183

Though I do notice that introducing these will leave the HTML-to-markdown converter unaware of these attributes. But as demonstrated above, markdown-it currently can’t handle markdown syntax representing these anyway. For that, it may be desirable to go a step further and implement list types in CommonMark…

2 Me gusta

There are no plans for this.

The lack of this makes it very difficult to quote official documents, legal documents, software licenses, or anything else which use non-number markers for document references.

1 me gusta

Add a wrapper to those lists and some CSS

In posts use:

[wrap="letterlist"]
1. is the first
2. is the second.
3. is the third
[/wrap]

IN your theme add:

.cooked div[data-wrap="letterlist"]
  list-style: upper-alpha;
}
1 me gusta

That’s a good solution if the goal is arbitrary list decorations, but the HTML type attribute is specifically meant for semantically-meaningful situations where the difference between list markers are more than decorative. From <ol>: The Ordered List element - HTML: HyperText Markup Language | MDN

Unless the type of the list number matters (like legal or technical documents where items are referenced by their number/letter), use the CSS list-style-type property instead.

It’s a common enough need that although the HTML attribute was deprecated in HTML 4.01 (with justification of it being purely stylistic), it was subsequently re-introduced in HTML5 for the specific purpose of encoding reference lists as described by MDN.

1 me gusta

Intenté usar esta solución y funciona, corrigiendo el CSS a lo siguiente (a la primera línea le faltaba un ol {):

.cooked div[data-wrap="letterlist"] ol {
  list-style: upper-alpha;
}

Sin embargo, no puedo hacer que se muestre en la ventana de vista previa del editor, lo que será un problema para la mayoría de mis usuarios. He intentado inspeccionar con el navegador web y parece que el CSS personalizado no se carga ni se aplica a la vista previa (no soy un profesional en esto, así que podría estar equivocado).

¿Se te ocurre alguna manera de resolver este problema, @Falco?

1 me gusta

Creo que ahora se admite html:

  1. Esto
  2. Otra cosa
  3. Algo más
<ol type="A">
<li> Esto
<li> Otra cosa
<li> Algo más
</ol>

Y los tipos A, a, I, e i.

También reversed y start= de <ol>:

  1. Pan
  2. Patatas fritas
  3. Sandía
<ol reversed start="36">
<li> Pan
<li> Patatas fritas
<li> Sandía
</ol>

Parece que usar HTML de esa manera está deshabilitando la interpretación de Markdown dentro de <li>, por lo que no es realmente aceptable que lo proponga a los usuarios.

1 me gusta

Para hacer uso de formato adicional dentro de ellos, creo que también tendrías que usar la versión HTML, ya que no le gusta mezclar:

  1. Pan
  2. Patatas fritas
  3. Sandía
<ol reversed start=36>
<li> <b>Pan</b>
<li> <i>Patatas fritas</i>
<li> <strike>Sandía</strike>
</ol>

Lo sé. Como dije, no me parece aceptable proponer eso a mis usuarios; cambia completamente el marcado solo porque quieres una lista ligeramente diferente.

Ah, lamento que esa no sea una opción aceptable para ti.

Quizás si inicias un tema de Dev pidiendo ayuda para ajustar tu solución existente, alguien podrá ayudarte. :+1:

1 me gusta