You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Via #68. The easiest way to manage translations of a roadmap is to put translated files in a separate subfolder and to add a <base href="../" /> directive to translated files to fix relative links. Problem is the JS currently overrides that directive with the template header.
Bonus: preserve other directives such as <link> and <style>.
The text was updated successfully, but these errors were encountered:
tidoust
added a commit
to tidoust/media-web-roadmap
that referenced
this issue
Oct 18, 2017
This commit implements the following changes:
- Custom directives in the <head> are now preserved. This makes it possible to
set a different <base> but also to override the CSS as well as to insert JS
code if needed (fixesw3c#76)
- Given an empty <a data-featureid="[feature]"></a>, the code automatically
sets the content of the link to the name of the feature if it exists, in other
words the "feature" value in the "data/[feature].json" file, or to the title of
the underlying specification otherwise (fixesw3c#78)
- IDs are automatically generated for sections, feature paragraphs and
individual feature references. The code used was stolen from Respec (fixesw3c#95)
Via #68. The easiest way to manage translations of a roadmap is to put translated files in a separate subfolder and to add a
<base href="../" />
directive to translated files to fix relative links. Problem is the JS currently overrides that directive with the template header.Bonus: preserve other directives such as
<link>
and<style>
.The text was updated successfully, but these errors were encountered: