← Back to team overview

bzr-explorer-dev team mailing list archive

Documentation for running Explorer with other languages

 

Ian,

Please find attached a small file, named README-revised.txt.  It is Explorer's 
README.txt with some additions:

1. qbzr installation is recommended.
2. Instructions on how to run Explorer in other languages are appended.

I hope you will find the additions to the README.txt acceptable.  Also, 
as this is a very small change I hope you will accept this somewhat "non-
standard" procedure of merging a change to your work.

This additional text originated from Alexander reminding me how to operate  
Explorer in languages other than English.  He gave me the detailed 
instructions and asked me to include it in the documentation. 

With very best wishes,

OldAl.
bzr-explorer: GUI application for using Bazaar
==============================================

Dependencies
------------

Required packages are:

* Python 2.4 or later

* Bazaar 1.14 or later.

* QBzr 0.17 or later.

If you wish to use the applets provided via bzr-gtk, it should be
installed as well.


Installation
------------

The easiest way to install this plugin is to either copy or symlink the
directory into your ~/.bazaar/plugins directory. Be sure to rename the
directory to explorer (instead of bzr-explorer). Also copy or symlink 
gbzr (or a subset of it) into ~/.bazaar/plugins directory.

In the future, it is hoped this plugin will be installed by the various
platform-specific installers for Windows and OS X. For Linux, it is
hoped that it will be made available via the usual package management
systems, include Add/Remove on Ubuntu.


Testing
-------

To test the plugin after installation:

    bzr selftest explorer
 

Documentation
-------------

To view the documentation after installation:

    bzr help explorer
 
A User Guide will be provided shortly.


Developers
----------

If you'd like to help, see the ROADMAP.txt file in the doc directory.

Translations
------------
The bzr Editor has been translated to many languages. Running of the
Editor in any one of those languages requires at most two steps:

step 1
------
If it has not been done already, create the "mo" files:

As root make the explorer file pwd and execute the following command:

python setup.py build_mo

This will create the binary MO format files from the PO data files 
and store it in a separate subdirectory. This is done for all the 
languages which have the PO data files stored in the current directory.

This step will need to be repeated if PO data is changed.

step 2.
------

Precede the invocation of the Explorer by the specification of
the LANGUAGE environmental variable LANGUAGE=<language code>.
For instance, for Russian this would be

LANGUAGE=ru bzr explorer

For German,

LANGUAGE=de bzr explorer

For Lithuanian,

LANGUAGE=lt bzr explorer

If you wish to work in one language continually for some time, you may optionally change the LANGUAGE environment variable. For instance, to set it
to French, execute

export LANGUAGE=fr 

and then invoke the explorer as many times as you wish:

bzr explorer

Licensing
---------

This plugin is (C) Copyright Canonical Limited 2009 under the
GPL Version 2 or later. Please see the file COPYING.txt for the licence
details.

References