On Wed, 2023-01-04 at 14:39 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> Now, this works in our current setup, but it seems to me that there is
> an easier way to achieve this with "native" Texinfo tools: Instead of
>
> @node Translated
> @section Translated
> @translatio
On Mon, 2023-03-13 at 22:20 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> On Wed, 2023-01-04 at 23:36 +0100, Jonas Hahnfeld via Discussions on
> LilyPond development wrote:
> > 1. All @ref{Translated} become @ref{Origin}, but as far as I understand
> > that may actually be
On Sun, 2023-03-19 at 23:56 +0100, Federico Bruni wrote:
> Actually I was curious to check the html output rather than the changes
> in the source.
> If it doesn't break working links, it's fine for me.
In the parts I touched, it is almost generating identical HTML (except
for the links to unnumb
Il giorno lun 13 mar 2023 alle 22:20:12 +0100, Jonas Hahnfeld
ha scritto:
> I would like to see a test for a language in order to better
understand.
Here's a proof-of-concept for the French Usage Manual (sorry, if I had
correctly remembered that it was you and not Jean-Charles, I would
have
Hi all,
sorry for dropping the ball on this topic...
On Wed, 2023-01-04 at 23:36 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> On Wed, 2023-01-04 at 22:58 +0100, Federico Bruni wrote:
> > Il giorno mer 4 gen 2023 alle 14:39:47 +0100, Jonas Hahnfeld
> > ha scritto:
> >
Le 04/01/2023 à 14:39, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
Another advantage would be that each document is self-
contained, ie no more recompilation of all documentation for changes
that do not affect cross-references at all.
That would be a HUGE improvement!
O
Il giorno mer 4 gen 2023 alle 23:36:39 +0100, Jonas Hahnfeld
ha scritto:
On Wed, 2023-01-04 at 22:58 +0100, Federico Bruni wrote:
Il giorno mer 4 gen 2023 alle 14:39:47 +0100, Jonas Hahnfeld
ha scritto:
> The other two formats we care about for the translated
documentation
> are PDF a
On Wed, 2023-01-04 at 22:58 +0100, Federico Bruni wrote:
> Il giorno mer 4 gen 2023 alle 14:39:47 +0100, Jonas Hahnfeld
> ha scritto:
> > The other two formats we care about for the translated documentation
> > are PDF and HTML. Of the two, HTML is arguably the more complex one in
> > terms of in
Il giorno mer 4 gen 2023 alle 14:39:47 +0100, Jonas Hahnfeld
ha scritto:
The other two formats we care about for the translated documentation
are PDF and HTML. Of the two, HTML is arguably the more complex one in
terms of infrastructure for cross-references: For PDF, we just link to
the (transla
On Wed, 2023-01-04 at 14:39 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> What do people think, especially translators? Would this "annoyance" be
> acceptable if it provides a significant simplification of our
> infrastructure? Another advantage would be that each document
During the last months, I've played a bit with Texinfo and would like
to discuss some ideas / simplifications for our translated
documentation. The base assumption is that translated .info files are
not important, ie we only build and install the English versions. If
that's not the case, please let
11 matches
Mail list logo
