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

Localization #16

Closed
comzeradd opened this issue Feb 18, 2015 · 6 comments
Closed

Localization #16

comzeradd opened this issue Feb 18, 2015 · 6 comments

Comments

@comzeradd
Copy link

What will be used for localization? I did the first implementation work on the original project for using webL10n javascript library. I could help adding it here too.

@ralphbean
Copy link
Contributor

Hey! I cooked up my own thing that I think works pretty well.

You can extract a .pot file with the commands mentioned here: https://github.com/fedora-infra/asknot-ng#preparing-translations

Then I was going to push that to zanata to get translated .po files back.

When those get compiled in .mo files, the asknot-ng.py script will find those and generate distinct copies of the site for each language.

There is then a "Languages" menu on each page that will let you navigate to each different page.

If you have ideas about how to improve any of those pieces, I'd love the help.

@sils
Copy link
Contributor

sils commented Aug 15, 2015

Related: I'd recommend using rultor for merging PRs and automatically upload translations to zanata in the rultor script. If you also use rultor to make releases you can automatically deploy the page and pull translations from zanata before doing that - a fully automated workflow. We've set up this for coala-analyzer/coala and it's awesome, contact me if you want that so I can help.

@sils
Copy link
Contributor

sils commented Aug 15, 2015

related bug: #27

@ralphbean
Copy link
Contributor

I'd say a tentative "no" to rultor for now. We share the same 👍 review process across all the fedora-infra repos, so we'd need to talk about it more to make sure the team's on board. It's not open source, is it? That's not a blocker (we're using GitHub) but we're trying to minimize our proprietary tools (see https://pagure.io).

@sils
Copy link
Contributor

sils commented Aug 15, 2015

Rultor is open source, otherwise I wouldn't recommend it. We're trying hard
to switch to gitlab btw. but the lack of hosted continuous integration
makes it hard. Rultor is at https://github.com/yegor256/rultor/ .

2015-08-15 18:43 GMT+02:00 Ralph Bean notifications@github.com:

I'd say a tentative "no" to rultor for now. We share the same [image:
👍] review process across all the fedora-infra repos, so we'd need to
talk about it more to make sure the team's on board. It's not open source,
is it? That's not a blocker (we're using GitHub) but we're trying to
minimize our proprietary tools (see https://pagure.io).


Reply to this email directly or view it on GitHub
#16 (comment)
.

@hhlp
Copy link
Contributor

hhlp commented Dec 13, 2019

I recommend close this ticket:

@cverna

regards.,

@cverna cverna closed this as completed Dec 14, 2019
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

5 participants