<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.E-mailStijl18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=NL link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Hi Dirk,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>As an active Dutch translator I am sure willing to give this a try. But not being extremely familiar with the process of submitting changes, can you give a small explanation/steps on how to do this?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>I took a look into the repo and the setup itself is quite easy to understand. I was fairly happy with translations for the website on Transifex, but if this is so painful to process and use on the final website we might try something else (or use more automation?).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>I do hope that this will only be for the website and not for all translations in the end. I feel Transifex is still a great tool for translators, very easy to use, also for non-technical people which makes it easier to step in as a translator.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>The only thing I don’t really like in the repo is the </span><span lang=EN-US>desktop-release-bottom.MD include with the %if page.lang constructs. That is inconsistent with the other language folder layout, and will bloat over time with more languages. Maybe this is something you can look into, why not just a desktop-release-bottom.MD per language in the existing language folder? It does not seem like a real common file right now.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>The other that is not directly clear to me, the difference between posts and drafts. So is there is process that promotes a draft to a post? Why can a new announcement not already be in the _posts folder?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Peter</span><o:p></o:p></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b>Van:</b> subsurface <subsurface-bounces@subsurface-divelog.org> <b>Namens </b>Dirk Hohndel via subsurface<br><b>Verzonden:</b> dinsdag 28 april 2020 23:39<br><b>Aan:</b> Subsurface Mailing List <subsurface@subsurface-divelog.org><br><b>Onderwerp:</b> a different approach to release announcements and translations thereof<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>For the last few releases I have struggled with the convoluted infrastructure (which, of course, I have created - so this is all my fault) for publishing announcements. WordPress had to be hidden from the world (as we had way too many hacking attempts and the amount of time spent on keeping this secure and alive was ridiculous), the static export is nice but takes many manual steps and is pretty error prone. And the integration with transifex for translations was just painful for everyone involved (especially me).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Based on this. I am once again going to try something different. Something that's completely integrated with GitHub and should in theory make it easy for people to translate announcements and maybe even take over some of the maintenance work from me. Because that's one of the oddities here; several people over the years have offered to help -- but my setup just wasn't done in a way where it felt easy to give others access...<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As a result, we now have a <a href="http://GitHub.com/subsurface/">GitHub.com/subsurface/</a><a href="http://subsurface.github.io/">subsurface.github.io/</a> repo which then gets published as <a href="https://subsurface.github.io/">https://subsurface.github.io/</a> via GitHub pages. If this works out, this can apparently be reasonably easily integrated with our custom domain.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The goal right now is NOT to reproduce our website there. Instead I was hoping to just move our announcements to that URL and allow people to translate the through a simple pull request. If this turns out to be amazing and everyone loves it, then we can think about migrating (most of) the full website, but for now I wanted to focus on the announcements.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Posts are written in markdown - just like our README. And typically styling for announcements is so primitive that the syntax really shouldn't matter all that much. I have re-created the Subsurface 4.9.3 announcement and created a Subsurface-mobile 3.0 announcement (which had never been published anywhere) and have also added a draft for Subsurface 4.9.4. So far I have only populated a bare basics German translation (that needs a lot more work), and haven't populated any of the other translations, yet. But I think that the structure is pretty straight forward and should make it easy for others to step in and complete my work. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- there's a shared footer for desktop release announcements (aptly named _includes/desktop-release-bottom.MD) that tells people how to download binaries. I have this in three languages and it should be obvious how to add others. The use of variables like {{page.version}} should be quite easy to understand.<o:p></o:p></p></div><div><p class=MsoNormal>- posts are in subdirectories, currently we have en/ and de/, filenames are iso-date plus topic, translations are connected via a 'ref' tag in the front matter (for simplicity I tried to keep this very structured, e.g. subsurface-4.9.3).<o:p></o:p></p></div><div><p class=MsoNormal>- some terms have central translations (this includes the language short codes, names, and flags) in _config.yml, but in general most of the translation work likely consists of copying the English post into the right directory, keeping the ref in the front matter and translating the actual announcement text<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Maybe I'm underestimating the learning curve, but I'd love to hear what people think - and ideally some of you would try to add our most common translations (Dutch, Spanish, Portuguese - for those I have created languages, if you want to add a different one, you'll need to add another language block in _config.yml).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>/D<o:p></o:p></p></div></div></div></body></html>