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
Newest GitHub page for earthquake scenarios display syntax for each scenario.
For the new 13 scenarios, the download links are broken as its referencing v1.2.2 release asset which those scenarios did not exist, and only in v1.2.3.
The text was updated successfully, but these errors were encountered:
In commit bdb5170, docs/_data/dsra.yml
was restructured where scenario.title was changed from an English string
to two children nodes of "en" and "fr" to accommodate the French titles.
However, I failed to replace scenario.title with scenario.title[page.lang]
in the Markdown files accordingly, leading to strange display of scenario
titles such as {"en"=>"M7.1 Sidney (BC)", "fr"=>"M7,1 à Sidney (C.-B.)"},
for example.
FixesOpenDRR#84
Newest GitHub page for earthquake scenarios display syntax for each scenario.
![image](https://private-user-images.githubusercontent.com/59062243/260525832-71c7c5ac-dbe7-47b2-8688-1e5cea0bb026.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyNDA0NjEsIm5iZiI6MTcyMDI0MDE2MSwicGF0aCI6Ii81OTA2MjI0My8yNjA1MjU4MzItNzFjN2M1YWMtZGJlNy00N2IyLTg2ODgtMWU1Y2VhMGJiMDI2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA2VDA0MjkyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTIzYzg0OGQ1NDllZmMwMDczMmE5YWU0NWM0OThjYzcxNDU1ZWU0NWY3ZWEyZjk1NzhlYTJkNGQ5N2NmOTUyOTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.6QFrIFj98_ojOrOjMuH3C4Y8RUJla0NrxR-rR7SR0oo)
For the new 13 scenarios, the download links are broken as its referencing v1.2.2 release asset which those scenarios did not exist, and only in v1.2.3.
The text was updated successfully, but these errors were encountered: