darktable-org / dtdocs

darktable user manual
GNU General Public License v3.0
74 stars 74 forks source link

Fix typo: Lighroom #522

Closed lekum closed 1 year ago

paperdigits commented 2 years ago

Hi! Good catch on the typo, but we never ever edit PO files directly for dtdocs, they must be changed via weblate.

The change to the English markdown file can stay though.

Please amend your PR.

On September 14, 2022 11:22:29 AM PDT, "Alejandro Guirao Rodríguez" @.***> wrote:

You can view, comment on, or merge this pull request online at:

https://github.com/darktable-org/dtdocs/pull/522

-- Commit Summary --

  • Fix typo: Lighroom

-- File Changes --

M content/overview/sidecar-files/sidecar-import.md (2) M po/content.de.po (2) M po/content.eo.po (2) M po/content.es.po (4) M po/content.fi.po (2) M po/content.fr.po (4) M po/content.gl.po (2) M po/content.it.po (2) M po/content.ja.po (2) M po/content.nl.po (2) M po/content.pl.po (2) M po/content.pot (2) M po/content.pt_br.po (2) M po/content.uk.po (4) M po/content.zh_Hant.po (2) M po/content.zh_cn.po (2)

-- Patch Links --

https://github.com/darktable-org/dtdocs/pull/522.patch https://github.com/darktable-org/dtdocs/pull/522.diff

-- Reply to this email directly or view it on GitHub: https://github.com/darktable-org/dtdocs/pull/522 You are receiving this because you are subscribed to this thread.

Message ID: @.***>

lekum commented 2 years ago

PR amended, thanks @paperdigits for your comment.

paperdigits commented 2 years ago

Sorry to be such a picky turd, but the PO files can't change at all. If you can squash the two commits together, it should be fine. But any change to the PO files will screw up out translation app.

On September 14, 2022 12:49:01 PM PDT, "Alejandro Guirao Rodríguez" @.***> wrote:

PR amended, thanks @paperdigits for your comment.

-- Reply to this email directly or view it on GitHub: https://github.com/darktable-org/dtdocs/pull/522#issuecomment-1247229972 You are receiving this because you were mentioned.

Message ID: @.***>

lekum commented 2 years ago

No problem, I'll squash the two commits into one and force push. I supposed this decision could be done at merge (squash) time but no problem from my side.

elstoc commented 2 years ago

Better to keep the PR clean. Thanks