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

[REF] contributing: What with .pot file in i18n/ folder? #97

Closed
moylop260 opened this issue Aug 4, 2015 · 10 comments
Closed

[REF] contributing: What with .pot file in i18n/ folder? #97

moylop260 opened this issue Aug 4, 2015 · 10 comments
Labels

Comments

@moylop260
Copy link
Contributor

Now with the use of transifex... is unnecesary to add .pot file in i18n of modules.
The question is: What should be our guideline?
A) File .pot required in each module of oca.
B) Don't add .pot file never.
C) You can choose if add .pot file or not.

What do you think?

@pedrobaeza
Copy link
Member

Option C can be, because having the .pot file is not a blocking issue (although the script will regenerate it)

@dreispt
Copy link
Sponsor Member

dreispt commented Aug 4, 2015

.pot and .po files should be allowed: contributors can provide modules already with some translations, and thats a good thing.

@pedrobaeza
Copy link
Member

@dreispt We are talking specifically for pot files, that are auto-generated. po files indeed are allowed to provide translations directly without the use of Transifex.

@qtheuret
Copy link

I'm for Option C

@max3903
Copy link
Sponsor Member

max3903 commented Aug 25, 2015

C

@moylop260
Copy link
Contributor Author

Ok, I got it
Thank you.
Then you can choose if add .pot file or not.
Then we don't need to add a new conventions for that.
I close this issue.

@pedrobaeza
Copy link
Member

My opinion on this have changed since the issue, because I found somebody translating from an outdated POT file. I prefer now to remove entirely POT files (option B).

@sbidoul
Copy link
Member

sbidoul commented Sep 12, 2016

Let's keep the issue open, since there is also an ongoing discussion on the mailing list?

@sbidoul sbidoul reopened this Sep 12, 2016
@osvalr
Copy link

osvalr commented Oct 20, 2016

My option is C
Just because it will be replaced anyways and most developers will be adding (or modifying) it

@pedrobaeza
Copy link
Member

This is now outdated as new Weblate requires POT and PO. Closing.

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

No branches or pull requests

7 participants