Date: Sat, 09 Aug 2025 16:05:15 +0300 From: =?UTF-8?B?VmxhZGxlbiBQb3BvbGl0b3Y=?= <vladlenpopolitov@list.ru> To: freebsd-translators@freebsd.org Subject: =?UTF-8?B?VHJhbnNsYXRpb24gb2YgYXJ0aWxjZXMvY29tbWl0dGVycy1ndWlkZSwgaGVs?= =?UTF-8?B?cCBoZWVkZWQ=?= Message-ID: <1754744715.469023967@f127.i.mail.ru>
index | next in thread | raw e-mail
[-- Attachment #1 --] Dear colleagues, I have started the translation of the article The committers guide (articles/committers-guide) and stoped at inconsistent text after words « (the rest of ls.c has been omitted): » — the text of the code and paragraph text are mixed in the code block. The next code block actually does not have 4 dots «….» in the beginning, and the rest of the articles has problems with rendering and in Weblate. * in HTML rendering next text block: « The new code is first, and your code is second. The right fix here is to just add a #undef COLORLS_NEW before #ifdef and then delete the old changes:» is rendered in the code block. * in the Weblate the text fragments are imported with wrong type: code blocks are imported as plain text, the plain text is imported as code blocks (every next …. toggle the status in wrong direction). These different types have different formatting, it is harder to translate in Weblate (plain text needs also newlines in formatting, what is not necessary in normal conditions). It affects more than 100 text fragments in Weblate down to next table in the article (near the text ‘ The problem report (if any) which is affected (typically, by being closed) by this commit» in section 9.14 ) * the text fragments in Weblate with wrong type have also service words from original documents together with article text, what make translation harder. I suppose, it will make the generation of the final adoc file impossible without additional manual corrections. If the error in original EN article is fixed, it will require to regenerate the Weblate texts for this articles. It will affect the translation in ES language (only one language translated this document in the latest version). pt-br, fr, ru translations are based on obsolete versions of this article. I prepared the patch to fix this error: https://reviews.freebsd.org/D51843 Could you support in fixing this bug? I cannot move farther in translation of this document, if Weblate texts have to be regenerated to their correct content. Best regards, Vladlen Popolitov Russian translation team. [-- Attachment #2 --] <HTML><BODY><div>Dear colleagues,</div><div> </div><div> I have started the translation of the article The committers guide</div><div>(articles/committers-guide) and stoped at inconsistent text after</div><div>words «<span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important">(the rest of ls.c has been omitted):</span>» — the text of the </div><div>code and paragraph text are mixed in the code block.</div><div> </div><div> The next code block actually does not have 4 dots «….» in the beginning,</div><div>and the rest of the articles has problems with rendering and in Weblate.</div><div> </div><ol><li>in HTML rendering next text block: «<span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important">The new code is first, and your </span><br><span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important">code is second. The right fix here is to just add a #undef<br>COLORLS_NEW before #ifdef and then delete the old </span><br><span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important">changes:» is rendered in the code block.</span></li><li><span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important">in the Weblate the text fragments are imported with wrong type:<br>code blocks are imported as plain text, the plain text is imported<br>as code blocks (every next …. toggle the status in wrong direction).<br>These different types have different formatting, <br>it is harder to translate in Weblate (plain text needs also newlines in <br>formatting, what is not necessary in normal conditions). It affects<br>more than 100 text fragments in Weblate down to next table in <br>the article (near the text ‘</span><span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;text-align:left;background-color:rgb(255,255,255);float:none;display:inline!important">The problem report (if any) which is affected </span><br><span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;text-align:left;background-color:rgb(255,255,255);float:none;display:inline!important">(typically, by being closed) by this commit» in section 9.14</span><span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important">)</span></li><li><span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important">the text fragments in Weblate with wrong type have also service words</span><br>from original documents together with article text, what make translation harder.<br>I suppose, it will make the generation of the final adoc file impossible without<br>additional manual corrections. <span style="font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;color:rgb(68,68,68);font-family:"inter var",-apple-system,BlinkMacSystemFont,"avenir next",avenir,"segoe ui","helvetica neue",helvetica,Cantarell,Ubuntu,roboto,noto,arial,sans-serif;background-color:rgb(255,255,255);float:none;display:inline!important"> </span></li></ol><div>If the error in original EN article is fixed, it will require to regenerate the Weblate</div><div>texts for this articles. It will affect the translation in ES language (only one language</div><div>translated this document in the latest version). pt-br, fr, ru translations are based on</div><div>obsolete versions of this article.</div><div> </div><div>I prepared the patch to fix this error:</div><div><a href="https://reviews.freebsd.org/D51843">https://reviews.freebsd.org/D51843</a></div><div> </div><div>Could you support in fixing this bug? I cannot move farther in translation of this document,</div><div>if Weblate texts have to be regenerated to their correct content.</div><div> </div><div>Best regards,</div><div> </div><div>Vladlen Popolitov</div><div>Russian translation team.</div></BODY></HTML>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1754744715.469023967>