Bug #170

Make template handle normal \pn useage

Added by john hatton almost 4 years ago. Updated over 1 year ago.

Status:Closed Start:
Priority:High Due date:
Assigned to:Cambell Prince % Done:

0%

Category:application Spent time: -
Target version:V0.13
Resolution:

Description

Chuck Grimes's data (and the MDF manual) use \pn like this:

\lx ama
\ps n
\pn kb
\ge father

The current template flags the \pn as a problem. The solution appears to be to give it the same structure as \ps, which allows it to have \lx as a parent.


Related issues

related to Bug #427: alternate hierarchy should default to multiple ps per sn Closed 05/09/2010
related to Bug #171: In alternate hierarchy template, let \sd have lx as a parent Closed
related to Bug #432: Templates need to match the official standards more preci... Closed 05/31/2010

History

Updated by john hatton almost 4 years ago

Replying to [ticket:169 hatton]:
Also, the \sn then needs to be changed to accept \pn as a parent.

Updated by J C almost 2 years ago

But when importing such things (part of speech, semantic domain) into FLEx, isn't it usually best to stick with one analysis language (usually English) and not even bother to import the other? Given that assumption, perhaps pn should be a sister of sn, that is, a child of ps. A missing ps would then be flagged as incomplete.

I haven't done enough with MDF, nor enough imports into FLEx, to speak with much authority on this. But this is one impression I have (from reading Beth B's import instructions, I believe).

-Jon

Updated by J C over 1 year ago

See also:
http://projects.palaso.org/issues/show/427
http://projects.palaso.org/issues/show/171

Maybe we should document all suggested template changes under issue 427?

Updated by Beth Bryson over 1 year ago

Yeah, I think FLEx doesn't currently have a way to import POS in more than one language. Usually I harvest the info ahead of time, and then pre-set the categories in FLEx. Then I only import one language of the POS fields. When there is a one-to-one mapping of English to national labels, that works fine. But there isn't always. For me, when I do an import, this requires fixing by hand with Bulk Edit after import. To really handle not having a one-to-one map here (which some argue for), FLEx would need a model change... But that's not relevant to you at the moment.

Updated by Cambell Prince over 1 year ago

  • Target version changed from V0.11 to V0.13

Updated by Cambell Prince over 1 year ago

  • Status changed from New to Resolved

Updated by Cambell Prince over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF