1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
======================================
QBzr - Qt-based front end for Bazaar
======================================
Requirements
============
* Python 2.4, 2.5 or 2.6
* Bazaar VCS itself
* PyQt 4.3 with Qt 4.3 or later
http://www.riverbankcomputing.co.uk/pyqt/
http://www.trolltech.com/products/qt
* Pygments v.1.0 or higher (optional, needed for syntax highlighting)
http://pygments.pocoo.org/
* PyEnchant (optional, needed for spellchecking in qcommit)
http://pyenchant.sourceforge.net/
Other bzr plugins that improve QBzr
===================================
* bzr-search (Makes searching in log faster)
https://launchpad.net/bzr-search
* bzr-difftools (Improves the usability of launching external diffs)
https://launchpad.net/bzr-difftools
Provided Commands
=================
* qannotate - GUI interface for file annotation
* qbrowse - Browse your branch a-la Trac Browse Source
* qcat - View the contents of a file as of a given revision
* qcommit - GUI interface to enter log message and select changes to commit
* qconfig - Bazaar configuration
* qdiff - Side-by-side and unidiff view of changes.
* qlog - Show log messages in GUI window.
* qpull - GUI interface for pull command
* qpush - GUI interface for push command
Interface localization
======================
QBzr uses gettext library for i18n support.
Available translations resides in po/ subdirectory of the tree.
QBzr expects to load binary mo-files from locale/ subdirectory
of the tree.
To generate translation POT-template file you need to run command:
python setup.py build_pot
All existing PO-files will be updated as well.
To compile translations to binary mo-files you need to run command:
python setup.py build_mo
NOTE: windows installer ships with latest compiled translation inside.
Help translate
~~~~~~~~~~~~~~
You can help to translate QBzr interface to other languages.
You can use either Launchpad trnaslations interface (it's preferable way)
see https://translations.launchpad.net/qbzr,
or you can translate it offline, see instructions below.
First at all you need to download from
http://bazaar.launchpad.net/~qbzr-dev/qbzr/trunk/files
either `po/qbzr-XX.po` (where XX is your language and country code)
or `po/qbzr.pot` if there is no po-file for your language yet.
Then you need to translate it either using any suitable text editor
with UTF-8 support or with tools like Poedit (http://www.poedit.net/)
or KBabel (http://kbabel.kde.org/).
When you're finish please file a bug report at
https://launchpad.net/qbzr/+filebug and attach the translated file.
To learn more about gettext and po-files see:
http://www.gnu.org/software/gettext/
Language and country codes listed in gettext manual:
http://www.gnu.org/software/gettext/manual/gettext.html#Language-Codes
http://www.gnu.org/software/gettext/manual/gettext.html#Country-Codes
Configuration
=============
The configuration is in .bazaar/qbzr.conf.
qlog_replace
~~~~~~~~~~~~
Multiline value containing regular expressions to replace text in commit
messages (useful to make clickable links to bug reports, ...). Can be used
for example by adding:
qlog_replace='''#(\d+)
<a href="https://launchpad.net/qbzr/+bug/\1">#\1</a>'''
to project/.bzr/branch/branch.conf.
diff_show_intergroup_colors
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Boolean value to allow painting interline changes in different colors
depend on the kind of change. Use values 'True' or '1' to enable option.
More Info
=========
* Bug Tracker, Source Code
https://launchpad.net/qbzr
|