Re: @xml:base with @rendition (and maybe other pointers)
"John P. McCaskey" <[email protected]> Sun, 7 May 2017 13:40:29 -0400
| Newsgroups | gmane.text.tei.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------81F24B058C908EA89A78F99C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Marin writes:
a) avoid @xml:base like the plague (as Hugh suggested)
Is that the best-practices consensus? Use regex and prefixDef instead?
I myself would lead encoders down this path for external links:
1) @facs is where you put the name of the image file, like=20
=E2=80=9Chttp://www.university.edu/ourdept/ourproject/pg1.jpg=E2=80=9C. @=
target is where=20
you put your reference links, like=20
=E2=80=9Chttp://en.wikipedia.com/wiki/abraham_lincoln.com=E2=80=9C. You c=
an also use=20
https: and file:.
=E2=80=9CWe don=E2=80=99t yet know the web server or directory where the =
images will be=20
stored. Can we just enter the .jpg file name and set the web directory=20
in one place later.=E2=80=9C
2) Yes, in <text> set xml:base to the images directory, e.g.,=20
=E2=80=9Chttp://www.university.edu/ourdept/ourproject/=E2=80=9C. Change i=
t there as=20
needed instead of trying to change every image link. Or put that in=20
<TEI> if this will affect the header as well.
=E2=80=9CWe can=E2=80=99t use just one base directory. Some images might =
be on one=20
server, some on another. We might want to have a different base=20
directory for <ref> elements and for <figure> elements.=E2=80=9D
3) OK, but now you=E2=80=99ll need to weigh pros and cons of two approach=
es=E2=80=94(3a)=20
multiple xml:base attributes and (3b) <prefixDef>. Here are the pros and=20
cons . . . .
Would others skip 2 and 3a and just go right to <prefixDef>?
John
--------------81F24B058C908EA89A78F99C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
<p><font size=3D"-1">Marin writes:</font></p>
<blockquote>
<p><font size=3D"-1">a) avoid @<a class=3D"moz-txt-link-freetext" h=
ref=3D"xml:base">xml:base</a> like the plague (as Hugh
suggested) <br>
</font></p>
</blockquote>
<p><font size=3D"-1">Is that the best-practices consensus? Use regex
and prefixDef instead?</font></p>
<p><font size=3D"-1">I myself would lead encoders down this path for
external links:</font></p>
<p><font size=3D"-1">1) @facs is where you put the name of the image
file, like =E2=80=9C<a class=3D"moz-txt-link-freetext" href=3D"ht=
tp://www.university.edu/ourdept/ourproject/pg1.jpg=E2=80=9C">http://www.u=
niversity.edu/ourdept/ourproject/pg1.jpg=E2=80=9C</a>.
@target is where you put your reference links, like =E2=80=9C<a c=
lass=3D"moz-txt-link-freetext" href=3D"http://en.wikipedia.com/wiki/abrah=
am_lincoln.com=E2=80=9C">http://en.wikipedia.com/wiki/abraham_lincoln.com=
=E2=80=9C</a>.
You can also use https: and file:.<br>
</font></p>
<p><font size=3D"-1">=E2=80=9CWe don=E2=80=99t yet know the web serve=
r or directory
where the images will be stored. Can we just enter the .jpg file
name and set the web directory in one place later.=E2=80=9C</font=
></p>
<p><font size=3D"-1">2) Yes, in <text> set <a class=3D"moz-txt-=
link-freetext" href=3D"xml:base">xml:base</a> to the
images directory, e.g., =E2=80=9C</font><font size=3D"-1"><font s=
ize=3D"-1"><a class=3D"moz-txt-link-freetext" href=3D"http://www.universi=
ty.edu/ourdept/ourproject/=E2=80=9C">http://www.university.edu/ourdept/ou=
rproject/=E2=80=9C</a>.
Change it there as needed instead of trying to change every
image link. Or put that in <TEI> if this will affect the
header as well.<br>
</font></font></p>
<p><font size=3D"-1"><font size=3D"-1">=E2=80=9CWe can=E2=80=99t use =
just one base
directory. Some images might be on one server, some on
another. We might want to have a different base directory for
<ref> elements and for <figure> elements.=E2=80=9D<=
/font></font></p>
<p><font size=3D"-1"><font size=3D"-1">3) OK, but now you=E2=80=99ll =
need to
weigh pros and cons of two approaches=E2=80=94(3a) multiple <a =
class=3D"moz-txt-link-freetext" href=3D"xml:base">xml:base</a>
attributes and (3b) <prefixDef>. Here are the pros and
cons . . . .<br>
</font></font></p>
<p><font size=3D"-1"><font size=3D"-1">Would others skip 2 and 3a and
just go right to <prefixDef>?</font></font></p>
<p><font size=3D"-1"><font size=3D"-1">John</font></font></p>
<br>
</body>
</html>
--------------81F24B058C908EA89A78F99C--