Re: Issues with ReSpec editor's drafts on Chrome, with fix

Thanks Richard, I'll make these changes to the BP doc and contact you if I have any questions.  Thanks for sharing.


On Jan 31, 2013, at 3:08 PM, Richard Cyganiak <> wrote:

> ACTION REQUIRED for all editors of documents that use ReSpec!
> There is an issue with the way we used ReSpec in at least *some* of our Editor's Drafts, including the DCAT spec. When you access the drafts in Chrome, they show up as raw unstyled documents, without any of the ReSpec stuff applied. To fix this in the DCAT spec, I added a copy of the latest ReSpec to our Mercurial repository, and made the following changes in the HTML header (removed lines starting with "-", added lines starting with "+"):
>  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
>  <!--[if lt IE 9]>
>  <script src=""></script>
>  <![endif]-->
> - <script type="text/javascript" src="" class="remove"></script>
> + <script type="text/javascript" src='../respec/respec3/builds/respec-w3c-common.js' class='remove'></script>
>  <script type="text/javascript" src="respec-ref.js" class="remove"></script>
>  <script type="text/javascript" src="../respec/gld-bib.js" class="remove"></script>
>  <script type="text/javascript" src="respec-config.js" class="remove"></script>	
> - <script type="text/javascript"  src="../respec/gld-config.js" class="remove"></script>
> Editors of all documents that use ReSpec should make the same changes.
> Best,
> Richard

Received on Thursday, 31 January 2013 20:12:44 UTC