{"id":388264,"date":"2024-06-29T07:50:22","date_gmt":"2024-06-29T07:50:22","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=388264"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=388264","title":{"rendered":"A new writing method\/technology (\u201cdendrowriting\u201d), as exemplified by the YearVer site<\/span>"},"content":{"rendered":"
<\/div>\n
\n
\n
\n
Several years have passed since the appearance of the first text markup language that supports \u201cdendrowriting\u201d<\/a>, but no worthwhile piece of text demonstrating the advantages of the new writing method\/technology has yet appeared.<\/p>\n

The largest \u201cdendrotext\u201d was a couple of paragraphs in the pqmarkup documentation<\/a>, consisting of only ~1300 characters and available only in Russian.<\/p>\n

In English there was no \u201cdendrotext\u201d at all, as such [<\/font>apart from small insertions in the documentation for the 11l programming language (e.g., \u2018Boolean type\u2019 in Built-in types<\/a>)<\/font>]<\/font>.<\/p>\n

But last year…
<\/a>
\u2026 when I was tidying up the meta-information<\/abbr> for my projects, I noticed that I had settled on recording version numbers in YYYY.M[.n]<\/code> form. Then I got the idea of giving this designation a name: YearVer [<\/font>obviously, by analogy with SemVer<\/font>]<\/font>. And the rule for naming additional versions {published in the same month or fixing bugs in the main version} formed the basis of the text for a new website.<\/p>\n

Soon after, I learned about the existence of CalVer from the Software versioning page on Wikipedia<\/a>. This disappointed me a little, but when I took a closer look I found out that calver.org<\/a> does not give any specific recommendations about which \u201ccalendar versioning\u201d scheme should be used, but simply describes the schemes already used in various projects, without highlighting them in any way.
The creation of a site for YearVer thus remained relevant, and I continued to fill it with content.<\/p>\n

The resulting description of the YearVer versioning scheme turned out to be quite short and concise, but very definite, offering specific schemes\/strategies depending on the type of project.<\/p>\n

And the most challenging task was now to translate the yearver.org\/ru page into English, preserving the formatting.<\/p>\n

To obtain a high-quality translation, I decided to contact three different translation agencies at once and to emphasize the fact that I was interested in maximum quality and prepared to pay extra<\/abbr> for it.
I contacted: <\/p>\n