#451 GeogFeat may contain lb

GREEN
closed-accepted
None
5
2013-04-29
2013-04-19
Jorge Fins
No

<lb/> should be available as a child of <geogFeat>.

Here is one example in Rabelais, Gargantua, Lyon, 1542 :
<geogName> <geogFeat>fo <lb rend="hyphen"/>rest</geogFeat> du <placeName>port Huault</placeName> </geogName>

Facsimile : http://www.bvh.univ-tours.fr/B360446201_B343_2/ecran/B360446201_B343_2_0279.jpg

Discussion

  • Lou Burnard

    Lou Burnard - 2013-04-19
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,9 +1,9 @@
    -<lb/> should be available as a child of <geogFeat>.
    +`<lb/>` should be available as a child of `<geogFeat>`.
    
     Here is one example in Rabelais, Gargantua, Lyon, 1542 :
    -<geogName>
    +`<geogName>
     <geogFeat>fo
     <lb rend="hyphen"/>rest</geogFeat> du <placeName>port Huault</placeName>
    -</geogName>
    +</geogName>`
    
     Facsimile : http://www.bvh.univ-tours.fr/B360446201_B343_2/ecran/B360446201_B343_2_0279.jpg
    
     
  • Lou Burnard

    Lou Burnard - 2013-04-19

    It is one of a select group of elements with macro.xText as content rather than macro.phraseSeq, presumably out of a desire for simplification. But I can see no justification for it being any different from e.g. geogName (which has macro.phraseSeq) so I am treating this as a corrigible error.

     
  • Lou Burnard

    Lou Burnard - 2013-04-19
    • assigned_to: Lou Burnard
    • Group: AMBER --> GREEN
     
  • Lou Burnard

    Lou Burnard - 2013-04-29
    • status: open --> closed-accepted
     
  • Lou Burnard

    Lou Burnard - 2013-04-29

    Content model changed to macro.phraseSeq at rev 12047

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks