Le 26/04/2020 à 09:46, Jonas Hahnfeld a écrit :
Am Samstag, den 25.04.2020, 21:53 +0200 schrieb Francisco Vila:
El 24/4/20 a las 17:18, Jonas Hahnfeld escribió:
However I'm pretty sure that many translations in the latter are dead:
As far as I understand we don't translate the docs by putting t
Am Samstag, den 25.04.2020, 21:53 +0200 schrieb Francisco Vila:
> El 24/4/20 a las 17:18, Jonas Hahnfeld escribió:
> > However I'm pretty sure that many translations in the latter are dead:
> > As far as I understand we don't translate the docs by putting the
> > strings in Documentation/po, but ra
El 24/4/20 a las 17:18, Jonas Hahnfeld escribió:
However I'm pretty sure that many translations in the latter are dead:
As far as I understand we don't translate the docs by putting the
strings in Documentation/po, but rather by copying the files and
translating them below Documentation/lang.
D
Am Sonntag, den 19.04.2020, 17:22 +0200 schrieb Werner LEMBERG:
> >> Is there a way to suppress them?
> >
> > Well, submitting fixes?
>
> I looked into both issues some time ago, but couldn't find out a good
> solution. Thanks to your clean-ups I can imagine that it's now easier
> to handle both
> It loads its languages from langdefs.py, and therefore outputs the
> following unhelpful warning:
>
> langdefs.py: warning: lilypond-doc gettext domain not found.
>
> I understand 'therefore' as 'expectedly' here.
Well, yes, but it's still annoying. Since I don't see any reason to
have thi
Am Montag, den 20.04.2020, 19:10 +0200 schrieb Francisco Vila:
> El 19/4/20 a las 17:12, Jonas Hahnfeld escribió:
> > IIRC langdefs.py complains that we set LANG=C
> > in the build process.
>
> Contributor manual says in website-build:
>
> %
>
> create-weblinks-itexi.py creates a loa
El 19/4/20 a las 17:12, Jonas Hahnfeld escribió:
IIRC langdefs.py complains that we set LANG=C
in the build process.
Contributor manual says in website-build:
%
create-weblinks-itexi.py creates a load of texi macros (of the order of
1000) similar to:
(...)
It loads its lan
>> Is there a way to suppress them?
>
> Well, submitting fixes?
I looked into both issues some time ago, but couldn't find out a good
solution. Thanks to your clean-ups I can imagine that it's now easier
to handle both problems.
> IIRC langdefs.py complains that we set LANG=C in the build
> p
>> [...] Is there a way to suppress them?
>
> I’ve been annoyed by these for quite some time as well. Is it worth
> opening a tracker page?
For me, it's not *that* annoying :-)
Werner
Am Donnerstag, den 16.04.2020, 12:14 +0200 schrieb Werner LEMBERG:
> Building lilypond you get a bunch of harmless but annoying
>
> langdefs.py: warning: lilypond-doc gettext domain not found.
>
> and
>
> .../podir-targets.make:14: warning: ignoring old recipe for
Le 19/04/2020 à 16:17, Valentin Villenave a écrit :
On 4/16/20, Werner LEMBERG wrote:
Building lilypond you get a bunch of harmless but annoying
langdefs.py: warning: lilypond-doc gettext domain not found.
and
.../podir-targets.make:14: warning: ignoring old recipe for target
'po-u
On 4/16/20, Werner LEMBERG wrote:
> Building lilypond you get a bunch of harmless but annoying
> langdefs.py: warning: lilypond-doc gettext domain not found.
> and
> .../podir-targets.make:14: warning: ignoring old recipe for target
> 'po-update'
> messages. Is
Building lilypond you get a bunch of harmless but annoying
langdefs.py: warning: lilypond-doc gettext domain not found.
and
.../podir-targets.make:14: warning: ignoring old recipe for target 'po-update'
messages. Is there a way to suppress them?
Werner
13 matches
Mail list logo
