openstack/horizon
Code Issues Proposed changes
OpenStack Dashboard (Horizon)
6,142 Commits 10 Branches 54 Tags 315 MiB
Python 63.1%
JavaScript 28.8%
HTML 6.5%
SCSS 1.5%
faae8b86fa
Go to file
Doug Fish faae8b86fa Pseudo translation tool 
A tool to allow pseudo translations to be created in order to identify
potential translation problems. To use the tool:
Make sure your English file is up to date:
./run_tests.sh --makemessages

Run the pseudo tool to create pseudo translations:
./run_tests.sh --pseudo de

Compile the catalog:
./run_tests.sh --compilemessages

Run your dev server. Log in and change to the language you pseudo translated.
It should look weird. More specifically, every translatable string is going
to start and end with a bracket and they are going to have some added
characters. For example, "Log In" will become "[~Log In~您好яшçあ]"
This is useful because you can inspect for the following:
- If you see a string in English it's not translatable. Should it be?
- If you see brackets next to each other that might be concatenation.
- If there is unexpected wrapping/truncation there might not be enough
  space for translations
- If you see a string in the proper translated language, it comes from an
  external source. (That's not bad, just sometimes useful to know)
- If you get new crashes, there is probably a bug. :-)

Implements blueprint: pseudo-translation-tool

Change-Id: If97754c2d4234b12b3d73616ff60527f6ad82d55
2015-01-20 13:08:26 -06:00
.tx Update .tx/config with type of files 2014-03-21 15:30:03 +01:00
doc Pseudo translation tool 2015-01-20 13:08:26 -06:00
horizon Merge "Imported Translations from Transifex" 2015-01-20 12:46:52 +00:00
openstack_dashboard Merge "Make ipmi meters be visible in Horizon" 2015-01-20 11:26:36 +00:00
tools Pseudo translation tool 2015-01-20 13:08:26 -06:00
.gitignore Remove compiled message catalogs 2014-10-10 05:31:32 +09:00
.gitreview Add .gitreview and rfc.sh. 2011-10-28 09:50:35 -04:00
.mailmap Update my mailmap 2013-10-25 14:49:23 +08:00
.pylintrc updating run_tests.sh to mimic other openstack projects, pep8, pylint, coverage 2011-08-31 14:41:36 -07:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:36 +00:00
HACKING.rst Remove #noqa from django.conf.urls.include 2014-09-29 13:58:39 +04:00
LICENSE Initial commit 2011-01-12 13:43:31 -08:00
Makefile Unifies the project packaging into one set of modules. 2012-02-29 00:20:13 -08:00
manage.py Gate on H102 Apache 2.0 license header not found for pep8 2013-11-19 13:55:04 -05:00
MANIFEST.in Drop NodeJS dependency in favor of pure-python lesscpy 2013-08-16 09:31:08 +02:00
openstack-common.conf Remove unused openstack.common.importutils 2014-10-13 15:15:31 -07:00
README.rst Add install guide for users and clean up README 2014-10-09 03:29:26 +09:00
requirements.txt Updated from global requirements 2015-01-13 00:03:35 +00:00
run_tests.sh Pseudo translation tool 2015-01-20 13:08:26 -06:00
setup.cfg Remove Python 2.6 classifier 2014-11-26 10:14:57 +01:00
setup.py Updated from global requirements 2014-05-01 13:44:26 +00:00
test-requirements.txt Updated from global requirements 2014-11-20 14:05:42 +00:00
tox.ini we don't need to allow insecure any more 2015-01-13 18:08:34 -05:00

README.rst

Horizon (OpenStack Dashboard)

Horizon is a Django-based project aimed at providing a complete OpenStack Dashboard along with an extensible framework for building new dashboards from reusable components. The openstack_dashboard module is a reference implementation of a Django site that uses the horizon app to provide web-based interactions with the various OpenStack projects.

Using Horizon

See doc/source/topics/install.rst about how to install Horizon in your OpenStack setup. It describes the example steps and has pointers for more detailed settings and configurations.

It is also available at http://docs.openstack.org/developer/horizon/topics/install.html.

Getting Started for Developers

doc/source/quickstart.rst or http://docs.openstack.org/developer/horizon/quickstart.html describes how to setup Horizon development environment and start development.

Building Contributor Documentation

This documentation is written by contributors, for contributors.

The source is maintained in the doc/source directory using reStructuredText and built by Sphinx

  • Building Automatically:

    $ ./run_tests.sh --docs

  • Building Manually:

    $ tools/with_venv.sh sphinx-build doc/source doc/build/html

Results are in the doc/build/html directory