You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
enhavo translates to “content”, which is totally not the same like “outline”. Skemo is the common one. Enhava tabelo can be a translation, if you focus on the common representation instead of semantics.
Sekcio as heading is debatable one. Sekcio like section is semantically narrower than heading. Whereas heading can concern the document title (HTML <h1>, LaTeχ \title) as well as some specific subelement (HTML <h6>, LaTeχ \paragraph), section is associated with something at between <h2> and <h4>. Titolo would be IMHO a bad translation, because titolo usually refers to the document title. Rubriko might be a better match. But titolo (unlike sekcio and rubriko) unambiguously only refers to the segment's title. I feel like there is no consensus and thus I keep the entry as is.
Email got introduced. Retpoŝto refers to the method. An alternative would be retmesaĝo which refers to the instance. I think the former fits better.
Telephone got introduced. Unambiguously, this is telefono.
Note that outline and heading are just the keys for the translations. The terms in the English locale are "Contents" and "Section". In particular, h1 and title are explicitly not covered by heading because in Typst these use the title element rather than the heading element.
I am clueless, but Claude says this about outline:
A full table of contents heading is typically written as "Enhavo" or "Enhavtabelo" (literally "contents table"), but "Enhavo" alone is the standard and most common heading used in Esperanto books and documents.
I haven't read a lot in Esperanto, so I can't really tell what the convention is, but la reta vortaro translates "skemo" to "schema", "model" or "structure", which is not a perfect fit. "Enhavtabelo" and "Tabelo de la enhavo" are both listed under "Enhavo" (the former being quoted from Zamenhof himself).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
i18nAbout language- or script-specific features. May need attention from native speakers.waiting-on-authorPull request waits on author
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Saluton,
enhavotranslates to “content”, which is totally not the same like “outline”.Skemois the common one.Enhava tabelocan be a translation, if you focus on the common representation instead of semantics.Sekcioas heading is debatable one. Sekcio like section is semantically narrower than heading. Whereas heading can concern the document title (HTML<h1>, LaTeχ\title) as well as some specific subelement (HTML<h6>, LaTeχ\paragraph), section is associated with something at between<h2>and<h4>.Titolowould be IMHO a bad translation, becausetitolousually refers to the document title.Rubrikomight be a better match. Buttitolo(unlikesekcioandrubriko) unambiguously only refers to the segment's title. I feel like there is no consensus and thus I keep the entry as is.Emailgot introduced.Retpoŝtorefers to the method. An alternative would beretmesaĝowhich refers to the instance. I think the former fits better.Telephonegot introduced. Unambiguously, this istelefono.Amike, tajpulo