New formatting for defining layouts #578
Labels
duplicate/out-of-date
Issues that are partially or entirely outdated or redundant in being superseded by later issues
feature
meta-issue
Overview issue with no *directly actionable* resolution
requires-backend-work
Requires work to Python, scripts, automation, etc.
requires-frontend-work
Work needs to be done on HTML, CSS, and/or JavaScript
requires-linguistic-work
get a linguist to deal with this!
@eddieantonio Here's a proposal for defining panes. Row and column labels are marked with
_
and|
, respectively (in comparison to<
and^
). Both labels, but in particular the column labels can have a hierarchy, which is used to organize the panes according to available space. One can also use the column labels to refer to the panes. What is not indicated as a label is a reference to an FST-generated form. In this format, the forms are specified in full, indicating the lemma slot with{{lemma}}
- this means that one would not necessarily need a separate specification/file for the paradigms and their generation.[edited to introduce row hierarchy as well]
The relabeling of the row and column labels, allowing for alternative schemes, is based on
crk.altlabel.tsv
. Space allowing, the two panes could be presented next to each other, in which case only one set of row labels would be necessary, and the column label for tense could be shared. If space would require the above to be presented in a single column vertically, then it would be a matter of UI design whether tense would be indicated as a column label for both panes, or only once.Originally posted by @aarppe in #167 (comment)
The text was updated successfully, but these errors were encountered: