-
ipsilon-tools-ipa-2.1.0-1.lbn25.noarch
Convenience client install tools for IPA support in the Ipsilon identity Provider
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
lasso-2.6.0-11.lbn25.x86_64
Lasso is a library that implements the Liberty Alliance Single Sign On
standards, including the SAML and SAML2 specifications. It allows to handle
the whole life-cycle of SAML based Federations, and provides bindings
for multiple languages.
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
lasso-python-2.5.1-7.lbn25.x86_64
Python language bindings for the lasso (Liberty Alliance Single Sign On)
library.
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
python-openid-cla-1.2-2.fc25.noarch
CLA extension implementation for python-openid
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
python-openid-teams-1.1-4.fc25.noarch
Teams extension implementation for python-openid
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
svrcore-4.1.3-3.lbn25.x86_64
svrcore provides applications with several ways to handle secure PIN storage
e.g. in an application that must be restarted, but needs the PIN to unlock
the private key and other crypto material, without user intervention. svrcore
uses the facilities provided by NSS.
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
svrcore-devel-4.1.3-3.lbn25.x86_64
svrcore provides applications with several ways to handle secure PIN storage
e.g. in an application that must be restarted, but needs the PIN to unlock
the private key and other crypto material, without user intervention. svrcore
uses the facilities provided by NSS.
This package contains header files and symlinks to develop programs which will
use the libsvrcore library. You should install this package if you need to
develop programs which will use the svrcore library.
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
svrcore-devel-4.1.3-3.lbn25.x86_64
svrcore provides applications with several ways to handle secure PIN storage
e.g. in an application that must be restarted, but needs the PIN to unlock
the private key and other crypto material, without user intervention. svrcore
uses the facilities provided by NSS.
This package contains header files and symlinks to develop programs which will
use the libsvrcore library. You should install this package if you need to
develop programs which will use the svrcore library.
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
svrcore-devel-4.1.3-3.lbn25.x86_64
svrcore provides applications with several ways to handle secure PIN storage
e.g. in an application that must be restarted, but needs the PIN to unlock
the private key and other crypto material, without user intervention. svrcore
uses the facilities provided by NSS.
This package contains header files and symlinks to develop programs which will
use the libsvrcore library. You should install this package if you need to
develop programs which will use the svrcore library.
Located in
LBN
/
…
/
Access and Identity Management
/
BastionLinux 25
-
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
