plone.intelligenttext
Overview
Provides transforms from text/x-web-intelligent to text/html and vice versa.
Line breaks and indentation are preserved, and web and email addresses are made into clickable links. Links get a rel="nofollow" to make this less interesting for spammers.
This package works in pure Python 2.7 and 3.0 and has no dependency on Plone.
Changelog
5.0.0 (2026-05-16)
Internal:
Update configuration files. [plone devs]
5.0.0a2 (2026-02-23)
Tests:
Skip the test extra. Latest tox will fail on it. [maurits]
5.0.0a1 (2025-11-19)
Breaking changes:
Replace pkg_resources namespace with PEP 420 native namespace. Support only Plone 6.2 and Python 3.10+. (#3928)
4.0.2 (2025-09-10)
Internal:
Move distribution to src layout [gforcada] (#4217)
Remove old way to run tests with setuptools [gforcada]
4.0.1 (2023-10-07)
Internal:
Update configuration files. [plone devs] (cfffba8c)
4.0.0 (2023-04-26)
Breaking changes:
Drop python 2.7 support. [gforcada] (#1)
Internal:
Update configuration files. [plone devs] (2ed8f544)
3.1.0 (2020-04-20)
New features:
Drop Python 2.6 support from tests. Start testing on 3.7 and 3.8. [maurits] (#9)
3.0.0 (2018-10-31)
Breaking changes:
Dropped support for Python 3.3.
Bug fixes:
Return str from transform in Python 3. [davisagli]
2.2.1 (2018-01-17)
Bug fixes:
Remove use of pyenv on Travis now that they upped their PyPy game and use the tox-travis egg to simplify how the config file looks like. [Rotonen]
2.2 (2017-08-04)
New:
Recognizes URLs embedded at the end of sentences. The punctuation mark of the sentence is split from the URL. Use brackets to force punctuation marks at the end of URLs. [tarnap]
Fixes:
Use pyenv for installing python versions on Travis. [Rotonen]
2.1.0 (2015-10-27)
New:
Make compatible with Python 3. [davisagli]
Fixes:
Minor cleanup (pep8, readability, ReST) [jensens]
2.0.3 (2015-05-11)
Minor cleanup: whitespace, git ignores. [gforcada, rnix]
2.0.2 (2013-01-01)
Allows an easy way to extend the converter through subclassing. One might want to override the regexps, or modify the HTML that one of the replace* methods produces. https://github.com/plone/plone.intelligenttext/pull/1 [dnouri]
Add MANIFEST.in. [WouterVH]
2.0.1 - 2010-07-18
Update license to GPL version 2 only. [hannosch]
2.0 - 2010-06-13
Package metadata cleanup. [hannosch]
2.0a1 - 2009-04-04
Specify package dependencies. [hannosch]
1.0.3 - 2009-04-09
Handle windows line endings. [elro]
URLs in html really should have the ampersand quoted. [elro]
Specify package dependencies. [hannosch]
1.0.2 - 2008-07-17
When convertWebIntelligentPlainTextToHtml is called with an explicit tab_width we try to make an integer of that (‘2’ -> 2). When that fails we use the default of 4. [maurits]
Minor change in code path, really only to get 100 percent test coverage. [maurits]
1.0.1 - 2007-12-04
Accept ip addresses as valid urls. [maurits]
Accept localhost as valid url. [maurits]
Recognize urls with port numbers as links. Fixes http://plone.org/products/poi/issues/156 [maurits]
If there is a url in brackets, the link should not contain one of the brackets. Fixes http://plone.org/products/poi/issues/155 [maurits]
Fix error where ampersands in urls would get html escaped. Refs http://plone.org/products/poi/issues/101 [maurits]
Accept input of None to our transforms. [maurits]
Add unit tests (mostly taken from Products.intelligenttext). [maurits]
1.0 - 2007-08-15
Released version 1.0. [diefenbach]
1.0b2 - 2007-05-07
Some documentation cleanup. [hannosch]
1.0-beta1 - 2007-04-07
Move into plone namespace and integration to PloneTransforms and MimetypesRegistry/ [diefenbach]
0.1
Initial development by Martin Aspeli (optilude@gmx.net). For further information see http://dev.plone.org/collective/browser/intelligenttext/
The transform was originally based on the url_to_hyperlink transform from Ploneboard by Plone Solutions and others.
Initial package structure. [zopeskel]
Metadata
Release files for plone.intelligenttext 5.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| plone_intelligenttext-5.0.0.tar.gz | 19.4 kB | Without provenance | Details for plone_intelligenttext-5.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plone_intelligenttext-5.0.0-py3-none-any.whl | Python 3 | none | any | Details for plone_intelligenttext-5.0.0-py3-none-any.whl |
Total release size: 29.2 kB
Release files / plone_intelligenttext-5.0.0.tar.gz
| Download URL | plone_intelligenttext-5.0.0.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c4b62fff3b6372ab99740a37215457038773b3a9bc8dc18eb731f35de068506
|
|
BLAKE2b-256 checksum How to use checksums |
d62d43a55526739bf05e41efa6c17f80c7bc2ff0566b6d9231c4893fdcec01ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / plone_intelligenttext-5.0.0-py3-none-any.whl
| Download URL | plone_intelligenttext-5.0.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0a1b7eccf1aa25eba6869331a9a84a941e1e9738a767638f1998547635f792f
|
|
BLAKE2b-256 checksum How to use checksums |
8ec36c376877145043cb463e496969cf60c84940cbe75d9bfa674f9950f9f88b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for plone.intelligenttext 5.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.