-
Products.PlacelessTranslationService-2.0.7-1.lbn25.noarch
What is PlacelessTranslationService?
------------------------------------
PTS is a way of internationalizing (i18n'ing) and localizing (l10n'ing)
software for Zope 2. It's based on the files supported by the GNU gettext set
of utilities. A good source of information and background reading is
the gettext documentation:
http://www.gnu.org/software/gettext/manual/
Using PlacelessTranslationService
---------------------------------
PTS is used in the following steps:
1. i18n your software
2. Prepare a translation template
3. Prepare translations of the template
4. Install translations
Each of these is explained below.
1. Internationalizing Your Software
A good overview of this can be found at:
http://www.upfrontsystems.co.za/Members/jean/mysite-i18n
2. Preparing a Translation Template
A translation template is an empty Portable Object file as defined
by the gettext standard with a special header block.
The PO format is described in detail here:
http://www.gnu.org/software/gettext/manual/html_node/gettext_9.html#SEC9
The header block is fairly self explanatory and can be seen in the
sample.pot file included in this directory. All phrases in capitals,
the language code, language name and (optionally) the content type
and preferred encodings should be replaced with their correct
values.
There are several ways to prepare a PO template:
-- By hand:
This can be done by copying the blank.pot included in this
directory, replacing the sample values as described above and and
then manually adding msgid and empty msgstr pairs for each of the
msgid's used in your software.
-- Using i18ndude:
i18ndude is a tool that is useful when all your software is in
the form of ZPT's that are stored in files on the filesystem.
It can be downloaded from:
http://plone.org/products/i18ndude
3. Prepare Translations of the Template
Preferably, find a translation company that can handle the gettext
standards and send them your .pot file. They should send back .po
files for the languages you require.
If you're doing it yourself, copy the .pot file to a file on the
name of the language you're translating to and with a .po
extension. Then go through that file and fill in the msgstr
sections. Finally, update all the metadata fields at the top of the
file so they are correct for the translation you have just
completed.
At this point, you should have a .pot file and a collection of .po
files.
4. Install Translations
PTS will look in folders called 'i18n' for .po files to use as
translations. These 'i18n' folders will be searched if they are in
the INSTANCE_HOME or in the directories of any of the Products you
have installed.
Copy your .po files to a 'i18n' folder of your choice in one of
these locations.
Once that's done, restart Zope.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python-BTrees-4.6.0-1.lbn25.x86_64
This package contains a set of persistent object containers built around
a modified BTree data structure. The trees are optimized for use inside
ZODB's "optimistic concurrency" paradigm, and include explicit
resolution of conflicts detected by that mechanism.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python-ZEO-5.2.2-1.lbn25.noarch
ZEO is a client-server system for sharing a single storage among many
clients. When you use ZEO, the storage is opened in the ZEO server
process. Client programs connect to this process using a ZEO
ClientStorage. ZEO provides a consistent view of the database to all
clients. The ZEO client and server communicate using a custom RPC
protocol layered on top of TCP.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python-ZODB-5.6.0-1.lbn25.noarch
The ZODB package provides a set of tools for using the Zope Object
Database (ZODB).
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python-repoze-2.3-1.lbn25.py37.noarch
Python moduel for repoze
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-persistent-4.7.0-1.lbn25.x86_64
This package contains a generic persistence implementation for Python. It
forms the core protocol for making objects interact transparently with a
database such as python-ZODB3.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
python2-zodbpickle-1.0.2-1.lbn25.x86_64
This package presents a uniform pickling interface for ZODB:
- Under Python2, this package forks both Python 2.7's pickle and cPickle
modules, adding support for the protocol 3 opcodes. It also provides
a new subclass of bytes, zodbpickle.binary, which Python2 applications
can use to pickle binary values such that they will be unpickled as
bytes under Py3k.
- Under Py3k, this package forks the pickle module (and the supporting C
extension) from Python 3.2, Python 3.3, and Python 3.4. The fork adds
support for the noload operations used by ZODB.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
repoze.errorlog-1.1-1.lbn25.noarch
This package implements a WSGI middleware filter which intercepts exceptions and writes them to a Python logging module channel (or the wsgi.errors filehandle, if no channel is configured). It also allows the browsing of limited exception history via a browser UI.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
repoze.lru-0.6-4.lbn25.py37.noarch
repoze.lru is a LRU (least recently used) cache implementation. Keys and values that are not used frequently will be evicted from the cache faster than keys and values that are used frequently. It works under Python 2.5, Python 2.6, Python 2.7, and Python 3.2.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
repoze.obob-0.4-6.lbn25.noarch
Zope-like publisher as WSGI application
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
