-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello,
Sorry, i just tried a fresh installation from the svn repo. I didn't put translations because they already are in the repo. It works, Bloodhound is translated, few words still need to be translated but it works. I think i have to use the svn repo instead of the 0.7 zip archive. Thanks, i would return to you if i need some other help ! Le 14/04/2014 09:14, Saint Germain a écrit : > > Hello, > > Last week, I was trying to solve the installation problems once and > for all with this ticket: > https://issues.apache.org/bloodhound/ticket/796 > > Normally it will be then much easier for those testing Bloodhound for > the first time. > > As for your specific problem (no translation), I haven't been able to > reproduce the problem. > > Can you try to follow this steps as nornal user (tested on linux, but > other platforms should be similar: > 1) Checkout the current svn repo: > svn co https://svn.apache.org/repos/asf/bloodhound/trunk/ bloodhound > > 2) Download an store the *.po files from transifex in the appropriate > directories (see previous email) > > 2) Create a virtual environment (for example with virtualenvwrapper): > mkvirtualenv --system-site-packages bloodhound > > 3) Go to the Bloodhound installer directory and run: > pip install -r requirements.txt > > 4) Check in the output that you can see the catalog generation > > 5) Check in the virtualenv directory (probably in ~/.virtualenv) that > you can find the *.mo files > > If you intend to regularly change/update the translation files (*.po) > it is recommended to install in dev mode instead. > > Let me know if this works, and we can continue if you have other questions. > > Regards, > > On 10 April 2014 14:04, Saint Germain <[email protected]> wrote: >> Hello Alexandre, >> >> I used i18n only with dev installation (requirements-dev.txt) so I >> haven't checked for normal installation, my mistake. >> I will try again this evening for normal installation to see what is >> going wrong. >> >> If you intend to work on translations, I would say that it may be >> better to also use dev installation. >> >> Thanks for reporting the issue and I am glad that someone is also >> interested in the french translation (that means that I haven't worked >> for nothing, yeah ! ;-) ) >> >> On 10 April 2014 11:37, Alexandre Papin <[email protected]> wrote: >>> I edited setup.py files to include locale folders and now locale folders >>> are respectively in their Bloodhound egg-info folder >>> >>> However the translation doesn't appear. >>> >>> I keep searching. If you have any idea of what i'm doing wrong, tell me ! >>> >>> Thanks (and sorry for spam..) >>> Le 10/04/2014 10:49, Alexandre Papin a écrit : >>>> >>>> Hum sorry for duplicate but in fact when I run python setup.py install >>>> in bloodhound_theme the egg generated in venv/lib/python2.7/site-packages/ >>>> contains bhtheme folder but this one doesn't contain locale folder. I >>>> think this is the problem. >>>> >>>> Le 10/04/2014 10:30, Alexandre Papin a écrit : >>>> >>>>> Hello, >>>> >>>>> Thanks for your help but i still stuck. >>>> >>>>> I already read the page you mentionned but the command line you told me >>>>> to use ask me an input file .. >>>> >>>>> So i search more deeply (args for compile_catalog) and so what I did : >>>> >>>>> Put bhtheme.po (which was for_use_bloodhound_bloodhound_theme_fr but i >>>>> renamed it) in bloodhound_theme/locale/fr/LC_MESSAGES/ >>>>> cd apache-loodhound-0.7/bloodhound_theme >>>>> python setup.py compil_catalog -d bhtheme/locale/ -l fr -D bhtheme >>>> >>>>> It worked, i have a bhtheme.mo now, so i did: >>>> >>>>> python setup.py to reinstall bhtheme. >>>> >>>>> I did these steps for dashboard, relations, multiproduct and search. >>>> >>>>> But when i look if these translations are implemented but no ! Nothing >>>>> change, i don't understand why.. >>>> >>>>> Oh and for option compile_catalog_js, it doesn't work, console told me >>>>> command not found.. >>>> >>>> >>> >>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTVifJAAoJEIzxlJ1HtoQq3hAIAJ02oUXr8lE8zBdBibIF0Gcr CnxQDZwovhvawX2OTO5HLqLp42KyDDDJhfshk5WCC37grHQSLgDEL0ASickZzZOS AYa8dnOXQmBtrdLBxsY8+AiwjTtFmpVjVGCv5if7fHba+JdHiuz0V6NefQBIZZuI 6DIDwS1U65Anm32wLNHpUWtQEc0qWjAk5QT+yFyca/dnAw0tRDbXsdu2RKY3FJb9 98OoL8l8Ox5ei1K0GUD8M+X1LGPygA0KWLn/VB91x+ARXcdho3OWyAa/OiquLUwZ DrkbDAs1VpTNgoQYz3Dk+nF9wYPOjEoL9MPz2s5FH+Z4UgImsVHE0DSxfWkEcuk= =0f+v -----END PGP SIGNATURE-----
