(For Oracc project managers)
If your Oracc project includes portal web pages that serve as introductory material to your corpus, you will need to ensure that they are valid XHTML 1.0 Strict before they can run on Oracc 2.
That sounds scary but it's not really. It just means that they are encoded so that all browsers can read and represent them correctly—and that Oracc 2's new full-text search can find and use them.
To find out more about how to check and convert your web pages, see the Oracc documentation on validating portal pages as XHTML Strict. If you use ESP to write your portal pages you don't need to do this, as ESP ensures XHTML Strict compliance as a matter of course.
As always, if you have questions or need help with any of this please just email me or a leave a comment here.
No comments:
Post a Comment