Hello,
On 2022-09-18 11:12, Patrick Shanahan wrote:
build failing on openSUSE Tumbleweed
/usr/bin/msgfmt: found 4 fatal errors
573 translated messages, 1141 fuzzy translations, 1341 untranslated
/messages.
gmake[2]: *** [po/CMakeFiles/locale_ro.dir/build.make:73:
/share/locale/ro/LC_MESSAGES/da
Hello!
I noticed that part of the strings do not show up in the .pot and
.po file:
darktable/po $ grep installer *
zh_CN.po:msgid "lua scripts installer dont show again"
zh_CN.po:msgid "lua scripts installer"
So, they're only in the zh_CN translation (which was last updated
in April, so maybe th
Hello,
One translator asked me about a part of the manual that
mentions channel #darktable at freenode -- he wants to know
if this is outdated, since everybody is moving away form freenode.
Is the IRC channel not being used anymore, and hence the information
could perhaps be removed from the manu
elect a language (pt_BR is already there) and start
> translating.
>
> -m
>
> On June 1, 2021 11:56:23 AM PDT, Jeronimo Pellegrini wrote:
>>Mica Semrick writes:
>>> Hi J,
>>
>>Hi!
>>
>>> The instructions on the dtdocs are still valid.
>>
Mica Semrick writes:
> Hi J,
Hi!
> The instructions on the dtdocs are still valid.
Ok!
> Weblate is the only option and will allow multiple contributors to
> work at the same time, so if everyone is using weblate, there doesn't
> not need to be any coordination, as weblate takes care of it.
B
Hello,
I have been focusing more on the translation of darktable itself, and
when I was about to give more attention to the manual, I incidentally
got messages from a few pt_BR users that said they'd like to contribute
I thought it would be nice to have more people involved (it would also
make the
Thank you!
I had not yet translated that part of the manual, it helps a lot.
J.
Andreas Schneider writes:
> On Thursday, 22 April 2021 12:32:56 CEST Jeronimo Pellegrini wrote:
>> Hello,
>>
>> While translating, I found a new word that I'm not sure I know
>> th
Hello,
While translating, I found a new word that I'm not sure I know
the meaning.
Is "brilliance" the same as "brightness"? Or, can I translate both
to the same word?
Below is the relevant part of the .po file...
Thanks!
Jeronimo
#: ../src/iop/colorbalancergb.c:1279
msgid "perceptual brillian
e
> is 100% translated, I believe.
>
> We can set that to whatever we'd like. What would be the advantage of having
> a partial translation go live?
>
> -m
>
> On March 5, 2021 5:27:51 AM PST, Jeronimo Pellegrini wrote:
>>Hello,
>>
>>I strated translating
Hello,
I strated translating the darktable manual into pt_BR
using the .po files directly and realized that, differently from when
docbook was used, now translations go live as soon as they're commited
(am I wrong?)
I also see that the default po4a "80%" default value as the minimum
for the trans
I think I get it now!
Feathering is as you described; the feathering *guide* uses
features from the image to change how feathering works, and
I was mixing up both.
Is that correct?
J.
Andrew Greig writes:
> Hi David,
>
> Feathering is the tapering-off of an effect from the hard line to the
>
Hello,
There is "feathering", used in mask refinement, which adapts
a mask's edge to edges detected in image.
And recently, when updating the translation, I saw "feather size"
referring to the radius of the outer circle (or ellipsis) when
creating drawn masks.
But those are not exactly the same.
Hi Pascal,
I did fetch, rebase, intltool-update, and it remains commented out.
I see it is not commented out in most languages:
$ grep "film stock" *
af.po:#~ msgid "film stock"
cs.po:msgid "film stock"
de.po:#~ msgid "film stock"
es.po:#~ msgid "film stock"
fr.po:msgid "film stock"
he.po:msgid "
KOVÁCS István writes:
> "following modules are deprecated because they have internal design mistakes "
> "that can't be solved and alternatives that solve them.\n"
> "they will be removed for new edits in next release."
> I'd actually re-phrase that (but I'm not a native speaker): for me,
> the
Hello;
This string was recently added to darktable:
"following modules are deprecated because they have internal design mistakes "
"that can't be solved and alternatives that solve them.\n"
"they will be removed for new edits in next release."
What exactly does the second line mean, specifically
omes at a cost of having to
> reword/retranslate parts of manual.
>
> wt., 20 paź 2020 o 18:00 Jeronimo Pellegrini napisał(a):
>
>> Hi Mica,
>>
>> Thank you for the work on getting a more modern translation
>> system. (And I'm really happy to see that Weblate is lice
e there
> are a lot of new writings, I don't think that the old translations will
> match up very well. I'm open to exploring machine translation for a
> first pass if you'd like to do that.
>
> I'm also open to any other suggestions you may have.
>
> Best,
Hello,
(I sent this from an email address different from the one
registered in the mailing list and it didn't seem to be
sent, so I'm sendingit again from the correct email. Sorry
for any duplicates)
I have been working on the pt_BR translation (of both darktable and
its manual). I usually tr
In which directory did you try?
I do it in the build/ directory, after building darktable.
J.
Maurizio Paglia writes:
> Ho Jeronimo,
> Unfortunately this is not the solution... Problem remains the same
> Maurizio
>
> Il mer 29 lug 2020, 11:08 Jeronimo Pellegrini ha
> s
Hello,
I am updating the translation of the manual, and
I see that the work "scope" was introduced in the
last few days.
I'd like to confirm this: in this context, "scope"
has the same meaning as "screen of a measuring
device", such as "the screen of a oscilloscope"
(hence the similar name). It d
Mica Semrick writes:
> Hi translators,
Hello!
> I've been working towards migrating the user guide into a more
> friendly format than docbook. I've come to the point where I need to
> define a translation workflow and was wondering what tooling everyone
> is using, so I can take that into accoun
On Thu, Apr 30, 2020 at 09:31:44PM +0200, Heiko Bauke wrote:
> Hi,
Hello!
> a lot of new features and enhancements have been brought to darktable
> recently. As a consequence there are also some new untranslated UI strings,
> which are not yet accounted for in the *.po files, not even as untrans
Hello,
I have been working on a translation of the user manual, and what
I have been doing is to work on the doc/usermanual/po/pt_BR.po
file. I can build the partially translated manual without problems.
But just now that I have made a first PR [0], I noticed issue
4177 [1], in which it is said
Hello,
I have been working on the pt_BR translation and found something I didn't
understand: in the right panel in lighttable view there is the metadata
editor. When it is exapnded, I see six fields:
title
description
creator
publisher
rights
notes
I have translated all these, except for the la
Hello,
Frido Claudino and I have finished (except for a couple of
strings) the translation into Brazilian Portuguese.
Now, I see that there there is a "translator-credits" string;
and we have used the previous work of Guilherme Brondani Torri.
Is that string supposed to hold the names of all trans
ion(at the end of the year) all
> is done.
> Please contact me asap.
>
> Frido
>
> On Sat, 2018-10-06 at 15:01 -0300, Jeronimo Pellegrini wrote:
> > Hello,
> > I see that the pt_BR translation was removed from some of the
> > recentreleases, and pt_BR.po doesn&#
Hello,
I see that the pt_BR translation was removed from some of the recent
releases, and pt_BR.po doesn't seem to have been modified in quite some
time.
Did the pt_BR translator stop working on it? I would be willing to help,
but I'm not sure if it's really needed, or if someone's already working
27 matches
Mail list logo
