book preview

[tuurma]

Summary of remaining issues

• [x] continuous numbering through different places (achieved via TeX)
• [x] shorthand for repeating dating sections between entries (~) (achieved via TeX)
• [ ] shorthand for repeating bibliography sections between entries (ib.)
• [x] small-caps for BC/AD
• [x] sub-formatting of bibl. entries (eg small caps for vol numbers etc)
• [ ] secondary sources handling
• [ ] some superfluous whitespace in final bracket
• [ ] ordering of final bracket contents
• [x] handling uncertain places separately from main place entry
• [x] handling place modifiers (like territory/area)
• [ ] Unicode handling throughout
• [x] cases of more than II generations with the same name #238
• [x] handling of attested places
• [x] name type labels (eg nomen_proprium)
• [ ] non-bibliographical abbreviations (eg pap. for papyrus, Chr. for Christian etc) #244
• [x] FB alternative place information

Ordering of final bracket info.

Five fields are allowed, each separated by a colon, in the following order :-

i) Alternative place information (e.g. and Athens or resid. Delos) ii) Name as attested with further details in brackets (e.g. (gen.)) or separated by a dash (e.g. (- SEG) iii) Relationships including generation numbers for homonyms iv) Status, profession, religion etc. v) Editorial remarks (e.g. (date - Kinns))

A comma is used as a separator within one of these fields.

sources linking

+ secondary sources cf.

examples http://clas-lgpn2.classics.ox.ac.uk/cgi-bin/lgpn_search.cgi?id=V1-32661;style=xml http://clas-lgpn2.classics.ox.ac.uk/cgi-bin/lgpn_search.cgi?id=V1-50032&style=#

NB: in Sebastian's export, bibl had @rend attribute specifying the linking element for the new form a case needs to be addressed where a source correcting or repeating the already existing one needs to be added

[tuurma]

@JSBLGPN I have tried to upload the new draft of book proofing but unfortunately encounter very different behaviour on the server than on my local machine - since our server version of eXist database is quite old, I'd like to migrate us to the new version, which should help

Meanwhile, I will paste some screenshots here if you have some immediate comments.

I do have a list of outstanding issues still

• [ ] continuous numbering through different places
• [ ] shorthand for repeating dating and bibliography sections between entries (~ and ib.)
• [ ] old style numerals
• [ ] secondary sources handling
• [ ] some superfluous whitespace in final bracket
• [ ] ordering of final bracket contents
• [ ] handling uncertain places separately from main place entry
• [ ] handling place modifiers (like territory/area)

For some of these I have questions.

1. Ordering of sub-parts of the final bracket. In general, we have following final bracket composite parts:

• Roman ordinal (for individuals named same as their father/son)
• relationships
• content of the final bracket field from the editor
• name type (like nomen proprium etc)
• status section summary (office, religion etc)

Please let me know if the order above is correct.

2. References separator.

If an individual has more than one reference, how should they be separated? Just space, comma, semicolon? I do take into account linking formulas present in the form already.

first part of Ἄλφιος entry

[JSBLGPN]

1. Ordering of sub-parts in the final brackets are separated by colon with the exception of the name type that is put in round brackets right after content from the editor (see example): i. Content of the final bracket field from the editor ii. name type in bracket iii. Roman numerals iv. Relationships v. status

EXAMPLE: (Lat. Aur. Agathus (n.pr.?): IV s. Agathon III: freed.)

2. primary sources are separated by semicolons, then secondary sources after a semicolon + cf. EXAMPLE: IG II, 2200; IEph. 1245; cf. RE XIV (3); Hafmann p. 123 (stemma). If there are no primary sources, no cf. before secondary sources.

3. Comments: only a couple of things for the moment and more later: +there are abbreviations for terms like Christian (=Chr.), amphora (amp.), etc. +from the field "source in "primary sources", not all types of sources are recorded in the book. So literary text does not need mentioning (ex. the Abdos from Edessa above). --> We will provide with a list of abbreviations and what needs to be in the book at the end of the week.

[tuurma]

@JSBLGPN I have a question about ordering entries under the same name (please excuse that no Greek characters are showing yet, but I highlighted relevant fragments). I assume chronological order but should it be terminus ante quem in case of non-exact dating? Eg byz. (311 - 699) would order as 699?

Other question is formatting parts of the bibl. abbreviations, eg IGLS XIV.2 or SEG VII. In the first case the abbreviation is registered as IGLS XIV.2 while in the latter case we have SEG as abbreviation and VII as the beginning of the details field. In both cases, as far as I can see, we'd need to render the number part as small caps but there are no clues in our XMLs about it. Was it previously marked explicitly or an algorithm that tried to figure out which parts should be treated as numbers and thus formatted with small caps?

P217be5ed-379d-483b-93dc-d9da9a8fe387

[tuurma]

Follow up question is about meaning of _ sign in abbreviations, like this example Lörincz,_+Hilfstruppen

    <bibl ana="BP2" n="" type="LGPN" xml:id="Lörincz">
        <abbr>Lörincz,_+Hilfstruppen</abbr>
        <bibl>B. Lörincz, +Die +römischen +Hilfstruppen +in +Pannonien +während +der +Prinzipatszeit. I, +Die +Inschriften (Vienna, 2001)</bibl>
    </bibl>

[JSBLGPN]

Date order: should be for example byz. ; v-vi ad ; m. v ad ; 475 AD ; 485AD iii/ii bc; 215bc; ii bc; ii-i bc; f. ii bc...

[tuurma]

I've prepared a list for all registered bib.abbreviations http://clas-lgpn4.classics.ox.ac.uk:8080/exist/apps/lgpn-editor/modules/tools/listBiblAbbr.xq

We could go through it and mark which parts should be small caps, like we do + for italics perhaps? So far we use + for italics, ^ for superscript. Do you already have a convention in place for small caps? I'd suggest _ if it's not in use already.

[JSBLGPN]

Formatting abbreviations: small capitals were not marked. I suppose it was done through the book checking program.

[JSBLGPN]

I don't think the sign _ means something.

[JSBLGPN]

CheckingProgam.pdf

Here is the section of the manual for the checking program.

I suppose that is why we have patterns in the references subform.

[tuurma]

[JSBLGPN]

Chronological ordering: No. 3 has to come before no. 2.

For places: the second place is only used in the book when it is an alternative origin. In this case, it will be indicated as follows: (or Orchomenos). if attested at is used as a first place, an will come after the place name in the book: Athens if a place is queried (certainty): Athens? in the book the order of the entries will be Athens Athens? Athens *

Thanks a lot.

[JSBLGPN]

[tuurma]

@JSBLGPN

Thanks, so I understand that in a case like this a person will be listed under Antioch and Orchomenos would not be mentioned at all

while if Orchomenos were marked as alternative origin, a person would be listed under Antioch as well but FB would start with (or Orchomenos)

Thanks for the reminder about ? and * places, just working on setting this up.

[tuurma]

Sample with alternative origin

[JSBLGPN]

Exactly...

[tuurma]

Here's first draft of treating ? and * in places

@JSBLGPN Follow up question is about places with a modifier like 'near' or 'territory', should it be listed under separate section, so

Athens Athens (territ.) Athens (near) Athens? Athens*

or listed under Athens but add territ. etc within the person entry?

Also, for places which are supposed to be grouped under the parent place like Kafr Buhum or Kišʻāla, should they be marked with territory? My apologies, I remember we spoke about it already but cannot find my notes.

[JSBLGPN]

places 'near' and 'territ.' should be listed under separate section:

Kišʻāla should be listed as in the picture. So the parent place here is Myra and dependent places Istlada, Mastaura...appear with no territory. Note that after Mastaura there is the modern place in brackets. This is when the assignation of an ancient place to a modern place is uncertain. Both ancient and modern names are indicated. I have a list of these ambiguous places for Syria.

[tuurma]

Thanks, I got this far with grouping places with modifiers (please disregard the last entry for Syria*, I know it's wrong)

[tuurma]

Fixed nesting of Syria*

[JSBLGPN]

-Ioudaia-Palaistine: in the form: ethnic. in book no asterix for ethnic, just "Ioudaia-Palaistine". Correctly put as a region in sample 2 -Arethousa (territ.): in the form: attested at, but in book no asterix for people with territ., just "Arethousa (territ.). -Beroia-Alab (ar.): in book should appear as Beroia-Alab (area), area in full

[JSBLGPN]

The rest is correct as far as I can see....

[JSBLGPN]

ERROR to my previous message: Arethousa (territ.) it should appear with a when in the form it is "attested at".

Very sorry.

Two more comments:

1. When in the form we have modern places, they should appear in the book followed by (mod.)

2. for ambiguous places: Example of how ambiguous places are encoded (the example Ad Ammontem which might be modern Kafr Hawar and is from Syria, from the territory of Damaskos). It should appear Ad Ammontem? (Kafr Hawar (mod.)).

[tuurma]

These are the options we have for relationship between a person and place.

So far I used the one with 'citizen' as the place to list person under, if such a an entry existed. If not, I would use the first place available but mark it with (which is why ethnic gave Ioudaia-Palaistine ).

1. Do I understand it correctly that 'ethnic' should be treated as 'citizen' and just be used without any marker?
2. Should all other options get an asterisk if they are the only ones available (say person has no ethnic/citizen entry but only 'resident of'?
3. What if there is an entry with both 'ethnic' and 'citizen', which gets precedence?

Got your remarks about modern and ambiguous places, many thanks, will propose a solution later today.

[JSBLGPN]

1. Yes ethnic should be treated as citizen
2. Resident and Attested at should get an asterisk. Alternative origin implies that there are one "citizen" and one "alternative origin". The alternative origin goes in the final bracket preceded by "or" (or Antioch).
3. Are there any cases like that? Can I have some examples? Thanks a lot

[tuurma]

Thanks, 1. and 2. are perfectly clear.

There are 3 cases with both 'ethnic' and 'citizen' entries

Ἀρταξίας Pe7344884-6062-4a24-a4e2-cdb199923315 Εὔβουλος P50f0439f-435c-476f-8f26-6105c1136a7b Γ. Ἰούλ. Ἀντίοχος Ἐπιφανὴς Φιλόπαππος Pb4a42faf-5f41-41ff-9eb4-9275b5e4a6ea

[JSBLGPN]

I checked and changed these entries, so this combination does not occur anymore. Philopappos has two citizenships, I will ask Richard what to do with these cases. Thanks

[tuurma]

Great!

Made the adjustments for ethnic, added (mod.) behind modern names. Next step I will handle the ambiguous modern/ancient names

[tuurma]

Btw there are 73 persons with double citizenship

[tuurma]

Here's my list of ambiguous places. Does it agree with yours?

http://clas-lgpn4.classics.ox.ac.uk:8080/exist/apps/lgpn-editor/modules/tools/ambiguousPlaces.xq (edited, gave wrong link the first time)

[tuurma]

Updated treatment of modern/ancient place names, still need to check if query marks for uncertainty are correctly preserved

was

now is

[tuurma]

Improved handling of uncertainty markers for place names

[tuurma]

Attaching two longer samples, sorry about the annoying lack of Unicode characters in Latin script, still trying to figure this out. I have tried to accommodate all your remarks regarding grouping entries into places and other place-related bits so if you spot something still amiss in this respect, please let me know.

I think now I will concentrate on the content of the FB part because this is where we might need quite some adjustments still.

I will leave formatting details (like styling parts of the references in small-caps etc) for last, since it least disturbs proofing process.

serg.pdf stefanos.pdf

[tuurma]

Ah, just remembered, I would need pointers for abbreviations - some will be about status entries (office, religion etc), some in types of sources but I'm sure there will be other... (cf. https://github.com/eXistSolutions/LGPN/issues/59#issuecomment-425818290)

From the same comment, I'm not sure if your remark about handling literary texts is already fully covered or not, here's the Abdos entry

[JSBLGPN]

1) Ioannes from Saba: this is correctly rendered.

2) Stephanos: correct Loukios: with two places: Akraba, Ad Ammontem. Only the first one (citizen) needs to be in, so this Loukios should only appear under Akraba. The second one (Ad Ammontem) does need to be in the book. Loukios: this is a duplicate, which I need to check on Monday.

3) List of ambiguous places: I will check the list on Monday. Sometimes the ancient name is queried, sometimes the modern names is queried. This expresses two different situations, but I think we will ignore the second situation (modern name queried).

4) List of Sergios and Stephanos: I will check on Monday.

5) Here is a first list of abbreviations, but I will give you a fuller list on the basis of the input form on Monday.

[tuurma]

3. I will add query marks to the list before you check

4. Don't waste too much time checking the long lists for Sergios and Stefanos in every detail (unless you really want to), just if something strikes you as weird. I will try to update the lists before Monday so you have the most recent version.

5. Thanks for the list, when you go through the input form it would be helpful if you give me field name before listing relevant abbreviations

[tuurma]

When you get to it on Monday, could you please let me know under what circumstances the shorthand for repeating bibl. entries (ib.) should be triggered? Does entire reference need to be identical or is it enough that the abbreviation is the same and details section may differ? To illustrate: in the example below should it be IGLS XXI.5 29 for the first ib. 50 for the second or IGLS XXI.5 50 for the second

[JSBLGPN]

ib.

Same book, different text IGLS XXI.5 29 -> IGLS XXI.5 29 IGLSXXI.5 50 -> ib. 50

Same book, same text, line numbers indicated IGLS XXI.5 29, 1 -> IGLS XXI.5 29, 1 IGLS XXI.5 29, 2 -> ib. l. 2

Same book, same text, no ligne numbers. IGLS XXI.5 29 -> IGLS XXI. 5 29 IGLS XXI.5 29 -> ib.

ib. is used continuously (no interruption between names) Leon IGLS XXI.5 29, 1 -> IGLS XXI.5 29 Letos IGLS XXI.5 29, 2 -> IGLS ib. l. 2

PS: don't forget to take into account references in brackets...see picture first case. Thanks

[JSBLGPN]

Double citizenship

For Philopappos above and the 72 other examples. The second citizenship should appear in the final brackets after and "and". Example : Apollonios...Petra...(and Damaskos) For Philopappos, Kommagene is the main citizenship and in the final brackets Besa should appear like this (and Athens, Besa). This is because Besa is a subdivision of Athens. The picture below gives you an illustration. Please put a comma between Athens and Besa. We could not put the comma with the old system. Thanks a lot

[tuurma]

Re double citizenship, understood, will implement this. For subdivisions, I will add its parent place if it is a deme.

Also thanks for the explanation about bibl. references. It's a bit more tricky but will work on it.

[JSBLGPN]

List of ambiguous places.

1). Comparing your list with mine, I can only see one missing: Telmenissos? Tall Mannis. Also missing is Akratai, which I am not sure it's a place name.

2). The list does not include the type "ancient place - modern place?" This type should appear as follow: Example: Dourbelenoi (Durbul (mod.)?). [so some place names are authorised in two different ways like Chauchaba no. 19 and can appear in both ways in the book]

3). The list does not include when hierarchy between places is queried. Example : No. 11 and also Mashara, perhaps in the territory of Paneas.

4). No. 12 (Sin) is strangely not in my list...perhaps it has been updated since...

5). No. 40 has been changed.

Thanks

[JSBLGPN]

PS: 2). for this one I said earlier that we would perhaps not need it, but I was wrong.

[tuurma]

1. Fixed the list generation to include cases like Telmenissos. Akratai is a place name, it just doesn't have a modern name and ancient is marked as uncertain http://clas-lgpn4.classics.ox.ac.uk:8080/exist/apps/lgpn-editor/editorPlace.xhtml?id=P7a1dd204-bdcd-4d43-9c27-8de453607759

[JSBLGPN]

I have not checked thoroughly the file for Sergios, but here are the main things I can see. Thanks a lot.

sergios.pdf

[JSBLGPN]

I will wait you update before checking Stephanos.

[JSBLGPN]

Here is a list of abbreviations and a few other things. Let me know if you have any question. Thanks a lot.

abbreviations_4JUN19.docx (Updated 4/6/2019 at 15.33) Sorry

[tuurma]

Thanks!

[tuurma]

Improved handling bibliographical abbreviations, listing under parent place where group option was used, handling of status/office/religion/profession as described in #244 and some other minor fixes