Thank you Hubert -- I hadn't realized that a considerable part of the
manual was already rewritten.
I'll wait for the new translation workflow then!
J.
Hubert Kowalski writes:
> Hi Jeronimo,
>
> Take a look at https://elstoc.github.io/dtdocs/ - as you'll see the manual
> there is reworded to
Hi Mica,
Thank you for the work on getting a more modern translation
system. (And I'm really happy to see that Weblate is licensed as
GPLv3!)
I would certainly want to still work with Emacs; not necessarily
with .po files. Just something that has an Emacs mode...
(I'm willing to help write an Ema
Hi Jeronimo,
Take a look at https://elstoc.github.io/dtdocs/ - as you'll see the manual
there is reworded to be more concise and to the point without additional
fluff and all contributors so far took measures to ensure that language is
clear english (both maintainers are native english speakers),
Hi Jeronimo,
Thank you for your all your work; last I had looked br_PT was the most
up-to-date.
We haven't really defined exactly what the translation workflow will
look like, but if we get feedback from translators that they still want
to work with PO files, I know we can certainly accommod
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
Sorry, I must not have explained myself well enough. For dtdocs, we have
pretty much chosen our tool chain, and we intentionally did not announce
anything to avoid this type of bike shedding.
While markdown has its negatives, the positive is that if you've written
a comment on the internet in
Before we open translations on weblate, I will take the current PO
files, for both the application strings and the user guide, and make
translation memory files out of them. I can then import them into
weblate (PO editor also supports TMX files in recent versions), and if
possible, translated s
On Sat, Oct 17, 2020, at 09:34, Pascal Obry wrote:
>
> Probably a good move and I understand that rewording was needed but
> that it is tad harsh for translators.
I may be optimistic/wrong here, but the situation for translators may not be
quite as bad as it sounds. From the parts of the re-worke
Le samedi 17 octobre 2020 à 09:28 +0100, Chris Elston a écrit :
> At a rough estimate you should expect the translations to end up
> perhaps no more than 50-60% complete in the best-case scenario.
Probably a good move and I understand that rewording was needed but
that it is tad harsh for translat
On 17/10/2020 08:25, Pascal Obry wrote:
I suppose one difficult point would be to reuse existing translation
but this is very important. The pr_BR manual is up to date and the
fr_FR one is 90% (was complete for 2.6). As translating the manual
needs countless hours we cannot tell the translators t
Hi johnnybit,
> I think it should be a separate repo under darktable org, same as
> dtorg website. That way dtdocs can have less technical but more
> writting oriented maintainers lowering the burden of keeping docs in
> main repo.
I don't agree with that since most of the documentation is wri
I think it should be a separate repo under darktable org, same as dtorg
website. That way dtdocs can have less technical but more writting oriented
maintainers lowering the burden of keeping docs in main repo.
sob., 17 paź 2020, 09:26 użytkownik Pascal Obry napisał:
>
> Congrats! I'm looking for
Congrats! I'm looking forward moving away from docbook.
I suppose one difficult point would be to reuse existing translation
but this is very important. The pr_BR manual is up to date and the
fr_FR one is 90% (was complete for 2.6). As translating the manual
needs countless hours we cannot tell
On 17.10.20 01:41, Mica Semrick wrote:
You have specifically pointed out where you think markdown is falling
short in this case.
For me MD vs Sphinx is mostly about roles, extensions, citations, line
comments, footnotes etc. that you have in Sphinx but not in MD.
MD was designed for writing te
You have specifically pointed out where you think markdown is falling
short in this case.
Feedback is welcome, but please try to make it actionable. We're aiming
for improvement.
On 10/16/20 4:38 PM, Moritz Moeller wrote:
On 17.10.20 01:30, Mica Semrick wrote:
On 10/16/20 2:12 PM, Moritz Mo
On 17.10.20 01:30, Mica Semrick wrote:
On 10/16/20 2:12 PM, Moritz Moeller wrote:
THB I think Markdown is a tad limited for docs like this.
Have you had a look at the site yet?
Yes I did.
Though I don't understand how that relates to the part of my reply you
quoted.
.mm
_
On 10/16/20 2:12 PM, Moritz Moeller wrote:
THB I think Markdown is a tad limited for docs like this.
Have you had a look at the site yet?
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsu
On 16.10.20 19:16, Chris Elston wrote:
Introducing dtdocs (https://github.com/elstoc/dtdocs)…
This project is a complete rewrite of the darktable documentation in
markdown, providing a number of advantages over the current user manual:
Fantastic! I suggested using Sphinx a few years back but
What can I say except - wow! I'm a fan since the start (because whatever I
tried I'm too dumb to do current docs). I hope weblate will work out for
translations (given that it seems that only pt_BR is translated on regular
basis currently)
pt., 16 paź 2020 o 19:16 Chris Elston
napisał(a):
> Intr
19 matches
Mail list logo
