search

eXistSolutions / LGPN

1 stars 0 forks source link

n.pr. should appear in brackets #293

Open tuurma opened 3 years ago

tuurma commented 3 years ago

n.pr. should appear in brackets. I wonder if it would work better if it was added as text in the Final Bracket field, rather than be indicated in the Type box in the Name field.

I could add brackets around, just for cases where FB doesn't contain anything else I'd need to strip them again. Is it a valid use case though? Just to have n.pr.? See last example below, Σαβαυν.

Current state:

image

image

image

Originally posted by @tuurma in https://github.com/eXistSolutions/LGPN/issues/292#issuecomment-758555574

tuurma commented 3 years ago

Πιστικός

image

Συδδηνος

image

Σαθηφελας

image

Σαβαυν

image

tuurma commented 3 years ago

Dear @RichardLGPN if you could check the above samples for FB with n.pr.? for correctness?

RichardLGPN commented 3 years ago

Example 1. n.pr.? should not be bracketed

Example 2. after (gen.) n.pr.? should be connected by long dash not bracketed : i.e. (gen.) -- n.pr.?

Example 3. Correct

From: Magdalena Turska notifications@github.com Sent: 27 January 2021 18:13 To: eXistSolutions/LGPN LGPN@noreply.github.com Cc: Richard Catling richard.catling@classics.ox.ac.uk; Mention mention@noreply.github.com Subject: Re: [eXistSolutions/LGPN] n.pr. should appear in brackets (#293)

Dear @RichardLGPNhttps://github.com/RichardLGPN if you could check the above samples for FB with n.pr.? for correctness?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/eXistSolutions/LGPN/issues/293#issuecomment-768474783, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEM3RZX2CJIKCBK6GE5C7WDS4BJUTANCNFSM4WVMVPIA.