Activity for Hugh A. Cayless
-
Hugh A. Cayless modified a wiki page
ReleaseProc
-
Schema
-
Schema
-
I'd argue we are almost exclusively marking up symbols on the surface.
-
A not-inconsequential part of my brain thinks using <hi> to indicate combining characters was a category error in the first place.
-
Schema
-
ReleaseProc
-
It was a relative link. I've re-pointed it to https://raw.githubusercontent.com/EpiDoc/Source/main/guidelines/xml/ex-epidoctemplate.xml. Going forward, the right solution may be to make sure the template gets copied alongside the HTML.
-
Consider nested ab for formatting changes
-
Schema
-
Home
-
LatestRelease
-
Updates for release 9.4.
-
Update TEI Stylesheets tag to latest.
-
Styl;esheets don't cope well with nested <hi>
-
Styl;esheets don't cope well with nested <hi>
-
Here's an example, modified from https://papyri.info/ddbdp/cpr;3;38. The usual problems of chaos with Arabic in XML obtain, of course. <div xml:lang="ar" type="edition" xml:space="preserve"><ab> <lb n="1"/><supplied reason="lost">بـ</supplied>ـسم الـ<supplied reason="lost">ـلّه</supplied> <supplied reason="lost">الرّحمن</supplied> <supplied reason="lost">الرّحيم</supplied> <lb n="2"/><seg xml:lang="grc"><supplied reason="lost">ἐν ὀνόματι τοῦ <expan>θ<ex>εο</ex>ῦ</expan> τοῦ ἐλεήμον</supplied><unclear>ος</unclear>...
-
Test EpiDoc GL process with new TEI Stylesheets
-
HTTPS error while running guidelines generation process
-
Using a relative path should be fine, so closing.
-
PR for space/gap
-
I think it probably shouldn't be a default, but an option, though not necessarily pegged to DDbDP style. I've been looking through our stuff and actually most of the line-spanning markup (apparatus, reg/orig, sic/corr, etc.) ends up coming out as strings. Like I said though, if is seems like an option people don't want in the core XSLTs, I'll just do it in papyri.info's.
-
Consider wrapping lines or line groups in HTML output
-
I've got some bilingual examples from papyri.info that have interspersed Greek and Arabic for which I think <seg> is way more appropriate than <foreign>. Happy to add one or two if that would be useful.
-
Christ, how did that ever slip through? I’ll fix it on the TEI side. 2 errors in one very small example! But yes, adding our own examples would be nice. On Jun 21, 2021, at 06:18, BODARD Gabriel gabrielbodard@users.sourceforge.net wrote: Nice! That makes it clear, for example, that we need to add our own examples to the ODD, since the <origdate> example in the TEI ODD is w r o n g .</origdate> [bugs:#182] Guidelines Spec pages broken Status: accepted Group: 9.1 Created: Mon May 17, 2021 11:44 AM...
-
Tom and I have sorted this out, I think. Commit [r2807] points at the compiled ODD instead of the plain one and so should pull in all the necessary info.
-
Pointing at compiled ODD.
-
XSLT2 error in squarebrackets regex
-
XSLT2 error in squarebrackets regex
-
This should be fixed. I have cherry-picked the commits from the DCLP pull request.
-
The red title on a brown background may be invisible to color blind readers, though I guess it's immediately repeated, so maybe they're better off...
-
Guidelines Spec pages broken
-
If you’re saying we should have tests, then I 100% agree. Even something as minimal as running a transform using the stylesheets without checking the results would have caught this. If you’re saying we need tests as a prerequisite for accepting the PR, then I think that will merely ensure it takes months to fix. I think we should treat the two concerns separately. On Mar 21, 2021, at 12:01, BODARD Gabriel gabrielbodard@users.sourceforge.net wrote: Excellent! Should we arrange a small group to look...
-
If I remember correctly, https://github.com/EpiDoc/Stylesheets/pull/10 contains a fix for this. Hugh On Mar 21, 2021, at 07:57, BODARD Gabriel gabrielbodard@users.sourceforge.net wrote: [bugs:#181] XSLT2 error in squarebrackets regex Status: unread Group: 9.2 Labels: xslt Created: Sun Mar 21, 2021 11:57 AM UTC by BODARD Gabriel Last Updated: Sun Mar 21, 2021 11:57 AM UTC Owner: nobody The stylesheet htm-tpl-sqbrackets.xsl is causing stacktrace errors in Saxon, and therefore not running. This line...
-
Tables
-
Here is a randomly chosen example from papyri.info: <lb n="11"/><app type="editorial"> <lem resp="BL 8.313"><supplied reason="lost"><g type="stauros"/> διʼ ἐμο</supplied>ῦ πανουφ<unclear>ίου</unclear></lem> <rdg><gap reason="lost" extent="unknown" unit="character"/> ὑπʼ <expan>Ἀνούφ<ex>εως</ex></expan></rdg> </app> <gap reason="lost" extent="unknown" unit="character"/> Comments: The content of@resp should be a URL. @resp should be @source. There really should be a @source on the <rdg> too—what this...
-
Here is a randomly chosen example from papyri.info: <lb n="11"/><app type="editorial"> <lem resp="BL 8.313"><supplied reason="lost"><g type="stauros"/> διʼ ἐμο</supplied>ῦ πανουφ<unclear>ίου</unclear></lem> <rdg><gap reason="lost" extent="unknown" unit="character"/> ὑπʼ <expan>Ἀνούφ<ex>εως</ex></expan></rdg> </app> <gap reason="lost" extent="unknown" unit="character"/> Comments: The content of@resp should be a URL. @resp should be @source. There really should be a @source on the <rdg> too—what this...
-
Here is a randomly chosen example from papyri.info: <lb n="11"/><app type="editorial"> <lem resp="BL 8.313"><supplied reason="lost"><g type="stauros"/> διʼ ἐμο</supplied>ῦ πανουφ<unclear>ίου</unclear></lem> <rdg><gap reason="lost" extent="unknown" unit="character"/> ὑπʼ <expan>Ἀνούφ<ex>εως</ex></expan></rdg></app> <gap reason="lost" extent="unknown" unit="character"/> Comments: The content of@resp should be a URL. @resp should be @source. There really should be a @source on the <rdg> too—what this...
-
Here is a randomly chosen example from papyri.info: <lb n="11"/><app type="editorial"> <lem resp="BL 8.313"><supplied reason="lost"><g type="stauros"/> διʼ ἐμο</supplied>ῦ πανουφ<unclear>ίου</unclear></lem> <rdg><gap reason="lost" extent="unknown" unit="character"/> ὑπʼ <expan>Ἀνούφ<ex>εως</ex></expan></rdg></app> <gap reason="lost" extent="unknown" unit="character"/> Comments: The content of@resp should be a URL. @resp should be @source. There really should be a @source on the <rdg> too—what this...
-
Here is a randomly chosen example from papyri.info: <lb n="11"/><app type="editorial"><lem resp="BL 8.313"><supplied reason="lost"><g type="stauros"/> διʼ ἐμο</supplied>ῦ πανουφ<unclear>ίου</unclear></lem><rdg><gap reason="lost" extent="unknown" unit="character"/> ὑπʼ <expan>Ἀνούφ<ex>εως</ex></expan></rdg></app> <gap reason="lost" extent="unknown" unit="character"/> Comments: The content of@resp should be a URL. @resp should be @source. There really should be a @source on the <rdg> too—what this...
-
Tom and I have been reviewing Pietro's PR and think at present it may need some modifications. Action on us to resume looking at it and get back to Pietro.
-
Added p5odds schema refs.
-
Corrected TEI subset URI to use HTTPS.
-
Notes re internal and external apparatus: Emmanuelle makes the excellent point that there's a cost/benefit tradeoff for projects deciding to do full parallel segmentation apparatus vs. simple notes on the text. For DLL, the carrot is that users get to play with the reading text using the apparatus. Gabby also points out that inline apparatus can be very useful for downstream applications that wish to do text processing (if they want to treat particular types of substitution, for example). There's...
-
Allow <restore>
-
We think this is resolved because EpiDoc now publishes our compiled ODD, allowing for chaining. I can explain how to do it (DLL does this), and there is a tutorial here: http://teic.github.io/TCW/howtoChain.html
-
span class=gap causes problems with square bracket handling
-
span class=gap causes problems with square bracket handling
-
I think I fixed this in r2727. Can someone check?
-
Switched datatype references to Pure Odd syntax.
-
Square-bracket-resolution code wasn't being called in examples.
-
There's no bug in the Stylesheets, and no issue that I can see with the use of span around gap. Which is not a DCLP thing, it's an RTL language thing, which I don't see as being a project-specific issue. You may disagree, but I'll argue with you. As far as I can see, what's happening is the Guidelines example transform simply doesn't call the square-brackets-removal template. I think this baffled me last summer, so I tabled it, and then forgot about it, for which my apologies. It baffled me, because...
-
EDAG agrees EpiDoc's use of <unclear> makes sense and agrees it should be more explicitly documented. <unclear> doesn't map perfectly to epigraphic practice in the use of underdot, but our use of the element is unambiguous.
-
span class=gap causes problems with square bracket handling
-
Will attempt to do (a)
-
Removed a bunch of duplicate @xml:ids.
-
Discuss issue of how inclusive EpiDoc should be
-
Use and document ODD chaining in releases
-
Did we release a compiled ODD in the latest version? If not, I will go do it...
-
Fix for anyElement issue.
-
Adding @source to schemaSpec.
-
Adding @source to schemaSpec.
-
ODD Chaining (see [#119]) will enable the creation of ODDs that derive from EpiDoc,...
-
The solution to [#119] should resolve this (though not add it to EpiDoc).
-
Use ODD chaining in releases
-
Use ODD chaining in releases
-
Use ODD chaining in releases
-
The source attribute will be inherited from the TEI 3.1.0 release (scheduled for...
-
Use ODD chaining in releases
-
Add Schematron rules to disallow [ ] ( ) and underdots
-
This might better be moved to a separate "EpiDoc" Lint Schematron. There are scripts...
-
Add Schematron rules to disallow [ ] ( ) and underdots
-
adjacent gaps broken if not both @extent=unknown
-
If you search the issues for "defaultVal" you'll see some of the work that's been...
-
This is being gradually done in the TEI by Syd and Martin Holmes, I believe. On Tue,...
-
adjacent gaps broken if not both @extent=unknown
-
Correcting a mistake hardly constitutes re-animation :-). We don't really follow...
-
Reinstate div/@type="figure(s)"
-
Fixed with r2464
-
Guidelines schema complains about sch and rng namespaces in EpiDoc ODD
-
Fix for [bugs:#137]
-
Removed extraneous bracket in title.
-
gap and Arabic
-
Closing. An issue arising from this was dealt with in #148
-
Removed extraneous message and more work on RTL...
-
Another update for bug 147.
-
Fixing [bugs:#147].
-
No, because there are more English words that might show up than Latin! Also, I think...
-
gap and Arabic
-
Fixed GreekKeys conversion
-
Remove temporary customization of m
-
@cause in att.transcriptional probably doesn't belong
-
att.textCritical on witDetail
-
Sourceforge Guidance doc out of date
-
Very likely. I don't know the half of what your brilliant stylesheets do :-) Sent...
-
I assigned it to Peter so he’ll be prodded to elaborate, not to implement it—which...
-
I assume Pure ODD, otherwise it wouldn’t make much sense. On Aug 12, 2015, at 11:15...
-
It would be nice to be able to generate this kind of documentation of any ODD. Probably...
1 >
