<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 30, 2020, at 3:59 AM, Peter Zaal via subsurface <<a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a>> wrote:</div><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class=""><div class=""><div class="">Reading this, it looks hard and scary - but it's actually just a hand full of steps, and most of them are only needed once.</div><div class="">And frankly, with this setup I'm equally happy if you were to simply edit the file (i.e., create a translation) and send that text to me in an email and I can take care of the mechanics.</div></div></div></blockquote><div class=""><br class=""></div><div class="">Ok, so now am at the point I have to admit that I am also a developer, so this is not scary at all ;)</div></div></div></div></div></div></blockquote><div><br class=""></div><div>Cool. Especially on Windows you still might prefer the GitHub Desktop version of all this (using VSC as external editor). But that's entirely up to you, of course.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class=""><div class="gmail_quote"><div class="">The reason I also asked for this is that there are probably some translators that are not developers or that technical. </div></div></div></div></div></div></blockquote><div><br class=""></div><div>There almost certainly are. We typically have far fewer translations of the announcements than of the app itself - which is fine, TBH.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class=""><div class="gmail_quote"><div class="">And for myself, I am a Microsoft .NET C# developer on the Windows platform, and have always been using Team Foundation Version Control (TFVC). My team and I have just recently started using Git repo's for version control. So I am really not that familiar yet with Git, so it's good to have a list of steps, even if it's just to verify I don't forget something (e.g. forking is not something we use).</div></div></div></div></div></div></blockquote><div><br class=""></div>I've been using git for about 16 years now and it all feels pretty natural and obvious to me - which is an interesting experience when I then try to explain it in detail.</div><div><br class=""><blockquote type="cite" class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class=""><div class="">The design with the desktop-release-bottom.MD file is indeed a bit odd. I'll figure out how to do this in a per-language manner. The reason for the existence of this include is that this is exactly the same in every announcement (and has been for quite a while), so it seems much easier to just include the text.</div></div></blockquote><div class=""><br class=""></div><div class="">I understand it's the same content for every announcement, but still different for every language. So it seems more natural to have a desktop-release-bottom.MD file per language. The same as there seems to be an about.MD file per language.</div></div></div></div></div></blockquote><div><br class=""></div><div>I haven't managed to figure out "relative" include paths in Jekyll. So the problem is that with this after a translator copies an announcement they also need to adjust the include statement.</div><div>But yes, I hear you. I'll figure out a way to not have this one file that's different.</div><br class=""><blockquote type="cite" class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class=""><div class="">Finally, the question about _posts and _drafts -- that's arbitrary. We could have the draft in the _posts folder. </div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div><div>Turns out this statement was wrong. With the plugin that we use, drafts MUST be in the _drafts folder</div><br class=""><blockquote type="cite" class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class=""><div class="">What makes a draft a draft is the fact that it doesn't have a date at the first part of the file name. Once we release, all I do is rename and move the files (that's a simply git operation) and push that change to the repo, then the files will automatically show up.</div></div></blockquote><div class=""><br class=""></div><div class="">Aha, was just wondering. If this is a manual step you want/have to do, all fine with me ;)</div></div></div></div></div></blockquote><div><br class=""></div>Correct - because we never quite know when a release will go out. I had been hoping to get it out tomorrow, but since we are still chasing an issue, that may not happen.</div><div><br class=""><blockquote type="cite" class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div dir="ltr" class=""><div class="gmail_quote"><div class="">I forked the repo, created a branch and started on the dutch translation. Will try to submit a PR tonight.</div></div></div></div></div></blockquote><br class=""></div><div>Awesome. Dank u</div><div><br class=""></div><div>/D</div><br class=""></body></html>