#3447 Adding br to the websites
Closed: Fixed None Opened 11 years ago by shaiton.

I remember that we need to edit few things in order to enable new languages on the websites.
but I forgot what..

The LINGUA file is fine.
build/translations.py should be updated (spread between all websites, right, we don't reuse only one? Manual edit?)

And I think that there is an other Apache conf somewhere in Puppet?

Check at http://start.fedoraproject.org/?lang=br

Thanks


Ok, I've seen the <website>-languages.conf files in puppet modules/fedora-web/files/. Is it the only files to update?

Is there a way to efficiently get all language codes?
(I am sure that we don't need only br).

Could not check that before next week.

I think thats the only place... it's per site tho, so the main fedoraproject has one file, fedorahosted another, etc.

Since we are in pre alpha freeze, this change would require a freeze break.

Would you like me to request one for it?

Yes I would like to. But I was not able to successfully build fpo with the right changes.
I should have forget something.
Any help appreciated.

I've only updated the language file for fedoraproject.org on the f18-alpha branch. It needs some puppet update but since it fails locally.. I haven't played with puppet yet.
You can try to build the br language.

Once resolved what is missing, I will do this on the master branch for the other websites.

I think languages.conf should be the only change needed to add a new lang.

What did you get in your local testing? errors? or just the language didn't work as expected?

The language switch failed (refresh in the previous language).
I am sure to have seen this before, but could not remember what was happening.

If you can take care of this, that would be great. (a local make all will give you the http conf to scp).
languages.conf was updated on the f18-alpha branch of fedoraproject.org.

I could be mistaken, but after LINGUAS file is updated, youll have to 'make clean' on your repo so it regenerates the languages.conf file.

Sure I had done that. On the staging websites (that is going to be online tomorrow), the LINGUA and the language.py files are up to date.

Could you check on your side guys? I don't know Apache really deap, and still have no idea what is missing.

Cheers,

ok, this should be live now and I think it's working...

Please reopen if you see problems with it.

Login to comment on this ticket.

Metadata