Closed nienna73 closed 2 years ago
Yes, it looks as it should. In the revised srseng dictionary DB I currently only have two columns, since the TVPB1 doesn't have the TAMA chunks, nor the LEXC-style lexical tier representation, so I'm just giving an example 3rd person singular verb form per aspect. But my understanding of the table implementation is that it really is up to the linguist how the table is specified and what content it has. One question I would have is how is the header row boldfacing specified? By <b>...</b>
tags in the table? I'm asking this as the code looked like it would remove such boldfacing fields.
The table specification is entirely up to the linguist, yes. The <b>
tags are removed for relabelling only, I do that so I can find the text from within them, but I don't actually remove them from the final product. So far, this is the only tag except from the regular table ones that is supported.
Ok, good - and I've added a revised version of the srs-to-eng DB, that makes use of the tabular format, cf. https://github.com/UAlbertaALTLab/morphodict/blob/main/src/srseng/resources/dictionary/srseng_test_db.importjson - so eventually we could update the DB on the production site.
Attention: Patch coverage is 0%
with 2 lines
in your changes missing coverage. Please review.
Project coverage is 78.06%. Comparing base (
db97405
) to head (6eb016a
). Report is 486 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
src/CreeDictionary/API/search/presentation.py | 0.00% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Relabelling for the info table seems to be working now. Here are the three different modes:
Linguist:
English:
Tsuut'ina:
@aarppe Does this look correct now?