Re: Building the Russian documentation

Gunter Königsmann via Maxima-discuss <[email protected]> Tue, 7 Jul 2026 09:25:28 +0200
Newsgroups gmane.comp.mathematics.maxima.general
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============2292829381624622174==
Content-Type: multipart/alternative;
 boundary="------------YgK3nxXCT82ODPIiXcAOqzai"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------YgK3nxXCT82ODPIiXcAOqzai
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Dear Viktor,

Exactly: The main problem of translating a document that is still alive=20
isn't the one-shot job but having an expert who keeps close track of any=
=20
change in the original for the next decades. Everything other than that=20
is just a workaround - and the least-effort workaround my branch=20
contains is an especially ugly one.

Kind regards,

 =C2=A0 =C2=A0 =C2=A0Gunter.

On 7/7/26 08:51, Viktor T. Toth wrote:
>
> Dear Gunter,
>
> I came across the same problem when I was last checking Maxima to see=20
> if it is ready for a new release. I opted NOT to corrupt the Russian=20
> docs for now, just tentatively drop them from the distribution build.=20
> I think that is the cleaner choice for the time being, until/unless=20
> someone whose Russian is much better than mine is willing to take a=20
> closer look. I know a bit of Russian but not enough to trust my=20
> skills, not even with AI assistance.
>
>
> Viktor
>
>
>
> On 2026-07-07 01:26, Gunter K=C3=B6nigsmann via Maxima-discuss wrote:
>>
>> Dear all,
>>
>> When trying to fix "make distcheck" I encountered the issue that
>>
>>   * texinfo by default errors out on missing internal reference
>>     targets and
>>   * the newest english documentation files reference stuff in the
>>     files that already have been translated to russian that still
>>     wasn't part of those files when they were translated.
>>
>> I asked AI to sort that out. It came up with the branch=20
>> KoenGu/RussianTranslationWorkaround that as a stop-gap adds a file=20
>> with all the=C2=A0 manual entries the english files the russian=20
>> documentation uses reference and that are missing from the russian=20
>> parts. I don't know if adding that commit to maxima would be a good=20
>> idea =3D> feel free to delete that branch or to merge it or to use it=
=20
>> for improving the russian documentation.
>>
>> Kind regards,
>>
>> =C2=A0 Gunter.
>>
>>
>>
>> _______________________________________________
>> Maxima-discuss mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/maxima-discuss
>
>
> _______________________________________________
> Maxima-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/maxima-discuss

--------------YgK3nxXCT82ODPIiXcAOqzai
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-=
8">
  </head>
  <body>
    <p>Dear Viktor,</p>
    <p>Exactly: The main problem of translating a document that is still
      alive isn't the one-shot job but having an expert who keeps close
      track of any change in the original for the next decades.
      Everything other than that is just a workaround - and the
      least-effort workaround my branch contains is an especially ugly
      one.</p>
    <p>Kind regards,</p>
    <p>=C2=A0 =C2=A0 =C2=A0Gunter.</p>
    <div class=3D"moz-cite-prefix">On 7/7/26 08:51, Viktor T. Toth wrote:<=
br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:[email protected]">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUT=
F-8">
      <p><font face=3D"monospace">Dear Gunter,</font></p>
      <p><font face=3D"monospace">I came across the same problem when I
          was last checking Maxima to see if it is ready for a new
          release. I opted NOT to corrupt the Russian docs for now, just
          tentatively drop them from the distribution build. I think
          that is the cleaner choice for the time being, until/unless
          someone whose Russian is much better than mine is willing to
          take a closer look. I know a bit of Russian but not enough to
          trust my skills, not even with AI assistance.</font></p>
      <p><font face=3D"monospace"><br>
        </font></p>
      <p><font face=3D"monospace">Viktor</font></p>
      <p><font face=3D"monospace"><br>
        </font></p>
      <p><font face=3D"monospace"><br>
        </font></p>
      <div class=3D"moz-cite-prefix">On 2026-07-07 01:26, Gunter
        K=C3=B6nigsmann via Maxima-discuss wrote:<br>
      </div>
      <blockquote type=3D"cite"
        cite=3D"mid:[email protected]">
        <meta http-equiv=3D"content-type"
          content=3D"text/html; charset=3DUTF-8">
        <p>Dear all,</p>
        <p>When trying to fix "make distcheck" I encountered the issue
          that=C2=A0</p>
        <ul>
          <li>texinfo by default errors out on missing internal
            reference targets and</li>
          <li>the newest english documentation files reference stuff in
            the files that already have been translated to russian that
            still wasn't part of those files when they were translated.</l=
i>
        </ul>
        <p>I asked AI to sort that out. It came up with the branch
          KoenGu/RussianTranslationWorkaround that as a stop-gap adds a
          file with all the=C2=A0 manual entries the english files the
          russian documentation uses reference and that are missing from
          the russian parts. I don't know if adding that commit to
          maxima would be a good idea =3D&gt; feel free to delete that
          branch or to merge it or to use it for improving the russian
          documentation.</p>
        <p>Kind regards,</p>
        <p>=C2=A0 Gunter.</p>
        <br>
        <fieldset class=3D"moz-mime-attachment-header"></fieldset>
        <br>
        <fieldset class=3D"moz-mime-attachment-header"></fieldset>
        <pre wrap=3D"" class=3D"moz-quote-pre">___________________________=
____________________
Maxima-discuss mailing list
<a class=3D"moz-txt-link-abbreviated moz-txt-link-freetext"
        href=3D"mailto:[email protected]"
        moz-do-not-send=3D"true">[email protected]</a>
<a class=3D"moz-txt-link-freetext"
href=3D"https://lists.sourceforge.net/lists/listinfo/maxima-discuss"
        moz-do-not-send=3D"true">https://lists.sourceforge.net/lists/listi=
nfo/maxima-discuss</a>
</pre>
      </blockquote>
      <br>
      <fieldset class=3D"moz-mime-attachment-header"></fieldset>
      <br>
      <fieldset class=3D"moz-mime-attachment-header"></fieldset>
      <pre wrap=3D"" class=3D"moz-quote-pre">_____________________________=
__________________
Maxima-discuss mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Maxima-discuss@lists.=
sourceforge.net">[email protected]</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.sourceforge.net/l=
ists/listinfo/maxima-discuss">https://lists.sourceforge.net/lists/listinfo=
/maxima-discuss</a>
</pre>
    </blockquote>
  </body>
</html>

--------------YgK3nxXCT82ODPIiXcAOqzai--


--===============2292829381624622174==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============2292829381624622174==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Maxima-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maxima-discuss

--===============2292829381624622174==--