Search results

Products.LinguaPlone-4.3.0-1.lbn25.noarch

LinguaPlone is the multilingual/translation solution for Plone, and achieves this by being as transparent as possible and by minimizing the impact for existing applications and Plone itself. It utilizes the Archetypes reference engine to do the translation, and all content is left intact both on install and uninstall - thus, it will not disrupt your content structure in any way. LinguaPlone doesn’t require a particular hierarchy of content, and will in theory work with any layout of your content space, though the default layout advertised in the install instructions will make the site easier to use. Some benefits of LinguaPlone Totally transparent, install-and-go. Each translation is a discrete object, and can be workflowed individually. Translations are kept track of using AT references. You can multilingual-enable your types without affecting their operation outside LinguaPlone. Even if you uninstall LinguaPlone after adding multilingual content, all your content will be intact and will work as separate objects! The only thing that will be inactive is the references between the objects. If you re-install it, they will be back. It’s very non-intrusive. Supporting multilingual capabilities is a 4 (!) line addition to your Archetypes class, and does not alter the functionality of the class when used outside LinguaPlone. Fully integrated with ATContentTypes, so the basic content types are translatable. Supports language-independent fields (example: dates, first/last names) for fields you want to be the same across translations, and updated in all languages if one of them changes. Uses the notion of canonical versions, so you can do interesting things with workflow, like invalidate all translations of a document when the master copy has changed.

Products.LinguaPlone-4.3.0-1.lbn25.noarch

LinguaPlone is the multilingual/translation solution for Plone, and achieves this by being as transparent as possible and by minimizing the impact for existing applications and Plone itself. It utilizes the Archetypes reference engine to do the translation, and all content is left intact both on install and uninstall - thus, it will not disrupt your content structure in any way. LinguaPlone doesn’t require a particular hierarchy of content, and will in theory work with any layout of your content space, though the default layout advertised in the install instructions will make the site easier to use. Some benefits of LinguaPlone Totally transparent, install-and-go. Each translation is a discrete object, and can be workflowed individually. Translations are kept track of using AT references. You can multilingual-enable your types without affecting their operation outside LinguaPlone. Even if you uninstall LinguaPlone after adding multilingual content, all your content will be intact and will work as separate objects! The only thing that will be inactive is the references between the objects. If you re-install it, they will be back. It’s very non-intrusive. Supporting multilingual capabilities is a 4 (!) line addition to your Archetypes class, and does not alter the functionality of the class when used outside LinguaPlone. Fully integrated with ATContentTypes, so the basic content types are translatable. Supports language-independent fields (example: dates, first/last names) for fields you want to be the same across translations, and updated in all languages if one of them changes. Uses the notion of canonical versions, so you can do interesting things with workflow, like invalidate all translations of a document when the master copy has changed.

Products.MailHost-2.13.1-2.lbn13.noarch

zope.sendmail integration for Zope 2.

Products.MailHost-3.0-1.lbn25.noarch

The MailHost product provides support for sending email from within the Zope environment using MailHost objects. An optional character set can be specified to automatically encode unicode input, and perform appropriate RFC 2822 header and body encoding for the specified character set. Full python email.Message.Message objects may be sent. Email can optionally be encoded using Base64, Quoted-Printable or UUEncode encoding (though automatic body encoding will be applied if a character set is specified). MailHost provides integration with the Zope transaction system and optional support for asynchronous mail delivery. Asynchronous mail delivery is implemented using a queue and a dedicated thread processing the queue. The thread is (re)-started automatically when sending an email. The thread can be started manually (in case of restart) by calling its manage_restartQueueThread?action=start method through HTTP. There is currently no possibility to start the thread at Zope startup time. Supports TLS/SSL encryption (requires Python compiled with SSL support).

Products.MailHost-3.0-1.lbn25.noarch

The MailHost product provides support for sending email from within the Zope environment using MailHost objects. An optional character set can be specified to automatically encode unicode input, and perform appropriate RFC 2822 header and body encoding for the specified character set. Full python email.Message.Message objects may be sent. Email can optionally be encoded using Base64, Quoted-Printable or UUEncode encoding (though automatic body encoding will be applied if a character set is specified). MailHost provides integration with the Zope transaction system and optional support for asynchronous mail delivery. Asynchronous mail delivery is implemented using a queue and a dedicated thread processing the queue. The thread is (re)-started automatically when sending an email. The thread can be started manually (in case of restart) by calling its manage_restartQueueThread?action=start method through HTTP. There is currently no possibility to start the thread at Zope startup time. Supports TLS/SSL encryption (requires Python compiled with SSL support).

Products.ManagableIndex-2.1.5-4.lbn13.noarch

Products.ManagableIndex is a framework for the easy construction of efficient, flexible, via the ZMI fully customizable indexes for Zope 2.11 (or above). It comes with a set of predefined indexes: Field, Keyword, Path, Range, Word and SimpleText index. Usually, they are more flexible and more efficient than the corresponding indexes from the Zope core. Products.ManagableIndex uses dm.incrementalsearch when it is installed. This can speed up queries by several orders of magnitude when used together with Products.AdvancedQuery

Products.ManagableIndex-2.1.5-4.lbn25.noarch

Products.ManagableIndex is a framework for the easy construction of efficient, flexible, via the ZMI fully customizable indexes for Zope 2.11 (or above). It comes with a set of predefined indexes: Field, Keyword, Path, Range, Word and SimpleText index. Usually, they are more flexible and more efficient than the corresponding indexes from the Zope core. Products.ManagableIndex uses dm.incrementalsearch when it is installed. This can speed up queries by several orders of magnitude when used together with Products.AdvancedQuery

Products.ManagableIndex-2.1.5-4.lbn25.noarch

Products.ManagableIndex is a framework for the easy construction of efficient, flexible, via the ZMI fully customizable indexes for Zope 2.11 (or above). It comes with a set of predefined indexes: Field, Keyword, Path, Range, Word and SimpleText index. Usually, they are more flexible and more efficient than the corresponding indexes from the Zope core. Products.ManagableIndex uses dm.incrementalsearch when it is installed. This can speed up queries by several orders of magnitude when used together with Products.AdvancedQuery

Products.Maps-3.3-1.lbn13.noarch

A Google Maps solution for Plone with the 'GeoLocation' content type. The main purpose of this product is to provide a very simple to use Google Maps integration for Plone. The following goals were set for development: * Ease of use o Add locations to a folder o Set the view of the folder to Map o It figures out how to center and zoom the map automatically * Flexibility for enhancement by using the Zope 3 component architecture * Sane fallbacks when Javascript is not available * Clean separation of javascript, templates and logic * Works on Smart Folders Additionally Maps has the following features: * Support for content which has a location set with the geolocation product

Products.Maps-3.3-1.lbn25.noarch

A Google Maps solution for Plone with the 'GeoLocation' content type. The main purpose of this product is to provide a very simple to use Google Maps integration for Plone. The following goals were set for development: * Ease of use o Add locations to a folder o Set the view of the folder to Map o It figures out how to center and zoom the map automatically * Flexibility for enhancement by using the Zope 3 component architecture * Sane fallbacks when Javascript is not available * Clean separation of javascript, templates and logic * Works on Smart Folders Additionally Maps has the following features: * Support for content which has a location set with the geolocation product