search

w3c / i18n-glossary

Definitions of terms used in W3C Internationalization documents.
https://w3c.github.io/i18n-glossary/
4 stars 4 forks source link

Link to external style sheet #39

Closed xfq closed 1 year ago

xfq commented 1 year ago

https://github.com/w3c/i18n-glossary/blob/bcf48194e99076ab258a1299378a964e955ef00b/index.html#L42

Currently, we link to a style sheet on GitHub, but the Pubrules doesn't allow this, because the link may be broken (for example, GitHub may be down or go bankrupt), so we should probably copy this file to this repo. This is also consistent with our Process.

If many of our documents use this file, we can also consider putting it on the W3C server and asking the Webmaster to add an exception.

r12a commented 1 year ago

If many of our documents use this file, we can also consider putting it on the W3C server and asking the Webmaster to add an exception.

We also have a way of automatically including the style sheet into the main html doc before publishing, which we also use for the gap analysis documents. That's what the data-import attribute is for.

xfq commented 1 year ago

If many of our documents use this file, we can also consider putting it on the W3C server and asking the Webmaster to add an exception.

We also have a way of automatically including the style sheet into the main html doc before publishing, which we also use for the gap analysis documents. That's what the data-import attribute is for.

Ah, OK. Have we applied this to i18n-glossary already?

r12a commented 1 year ago

Since Addison added it to a recent commit, afaict, no. We'd need to go through the first part of the publication process and look at the file in .tmp to check whether the styling is there.

aphillips commented 1 year ago

I fixed this today, switching to a style element with ReSpec's data-import attribute. I think you can close?

xfq commented 1 year ago

Yes. Thank you!