Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why is po_update() separate from po_extract()? #307

Open
maelle opened this issue Oct 31, 2023 · 2 comments
Open

why is po_update() separate from po_extract()? #307

maelle opened this issue Oct 31, 2023 · 2 comments

Comments

@maelle
Copy link
Contributor

maelle commented Oct 31, 2023

I might be missing something obvious but why is po_update() separate from po_extract() when we always have to run it after po_extract()?

@MichaelChirico
Copy link
Owner

They're definitely closely related... One reason to keep them separate is we might prefer the translator to do po_update() themselves because of the fuzzy/deprecated messages. The package author may have no context on whether a fuzzy message still makes sense after the update.

@hadley I notice now po_update() is not mentioned in either of the new vignettes. Do you have notes handy on the design here / should we add an explanation to the vignette(s)?

@hadley
Copy link
Collaborator

hadley commented Nov 3, 2023

Hmmmm, good question. Maybe po_extract() could automatically run po_update() if there are existing translations?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants