Skip to content

import, slice and callable need a rendering that survives the part of speech #61

Description

@tamnd

Left over from #58. Three keep_en rows that are the same shape as float was, and were not moved with it because naming one Vietnamese rendering would fail G02 on the other half of their entries.

term standalone entries what they are prose findings under G03
import 5 the statement, in the index of statements 13
slice 5 a glossary headword and an index category 5
callable 4 a glossary headword 4

Each of those 22 G03 findings is a correct translation being reported as a glossary violation, the same defect that #58 fixed for type and list. The reason they are still reported is that the Vietnamese moves with the part of speech and a row holds one string:

  • import is nhập as a verb, in "các tên cần nhập" and "muốn nhập một module", and stays import as a noun, in "hệ thống import".
  • slice is cắt as a verb, đoạn cắt and cắt lát as a noun, all three in the corpus and none of them a majority.
  • callable is an adjective, gọi được and có thể gọi, and G02 checks presence of one string.

G02 matches on presence rather than agreement on purpose, because Vietnamese inflects a phrase by the words beside it, but presence still needs one spelling to be present. So this is either a wording decision that picks the form that appears in every case, or a row that can carry more than one acceptable rendering, and those are different amounts of work.

Reading the 22 first would say which. If nhập appears in all 13 import entries and the noun cases are all inside markup, the row is just nhập with identifier and this is small.

  • Read the 13 import, 5 slice and 4 callable findings
  • Decide whether a row needs a second acceptable rendering, or whether one form covers each
  • Add the rows, or file the schema change

Metadata

Metadata

Assignees

No one assigned

    Labels

    auditThe deterministic check catalogueglossaryTerminology contract and the matcher

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions