James Cummings
What's happening?
-
Text Encoding Ini...
jcummings committed revision 10358 to the Text Encoding Initiative SVN repository, changing 1 files.
2012-05-15 08:11:41 PDT in Text Encoding Ini...
-
Text Encoding Ini...
jcummings committed revision 10356 to the Text Encoding Initiative SVN repository, changing 1 files.
2012-05-15 04:22:59 PDT in Text Encoding Ini...
-
Text Encoding Ini...
jcummings committed revision 10355 to the Text Encoding Initiative SVN repository, changing 1 files.
2012-05-15 03:53:05 PDT in Text Encoding Ini...
-
Comment: @rend from data.word to text
I think we're setting up a false dichotomy between 'allow any text' and 'constrain the values'. Currently the Guidelines *do* make a recommendation on this, and that recommendation is that these are discrete space-separated tokens. That some people are abusing this to add free text is in no way a logical justification for throwing out the existing recommendations. Yes, people can constrain...
2012-05-10 07:16:56 PDT in Text Encoding Ini...
-
Comment: @rend from data.word to text
I would be one of those arguing against this change. (And martin: Is arguing from the existence of poor programming really a good argument? Surely we should be pointing out this to google?) During the discussion I summarised some of my disagreements at http://blogs.oucs.ox.ac.uk/jamesc/2012/03/26/more-about-rend/ and earlier at...
2012-04-27 09:12:59 PDT in Text Encoding Ini...
-
Version numbers link to page about versions?
Should the version number (i.e. "Version 2.1.0" on the bottom of Guidelines generated pages actually be a link to a page explaining the version numbering system, listing all the releases (and those linking to the changelog of each release?). Alternatively, it could just point to the sourceforge download page, but I think that is less helpful. -James.
2012-04-27 09:05:15 PDT in Text Encoding Ini...
-
Comment: Non-Poetry example for <line>
apologies, SF opened two identical tickets because of accidental resubmission. bug 3522020 (duplicate of this one) deleted.
2012-04-27 07:47:17 PDT in Text Encoding Ini...
-
Non-Poetry example for <line>
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-line.html says: "This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use l) nor to mark linebreaks within text which has been encoded using structural elements such as p (for which use lb).&q.
2012-04-27 07:42:58 PDT in Text Encoding Ini...
-
Non-Poetry example for <line>
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-line.html says: "This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use l) nor to mark linebreaks within text which has been encoded using structural elements such as p (for which use lb).&q.
2012-04-27 07:42:52 PDT in Text Encoding Ini...
-
Comment: i18n revision due
Council 2012 f2f in Ann Arbor decides: Rahtz to implement and kick off ongoing internationalisation updates. Also to check FM1 to see if translator's list is up to date.
2012-04-18 08:26:07 PDT in Text Encoding Ini...