-
zope.html-2.4.2-3.lbn25.noarch
This package contains support for editing HTML and XHTML inside a web page using the FCKeditor as a widget. This is a fairly simple application of FCKeditor, and simply instantiates a pre-configured editor for each widget. There are no options to control the editors individually.
Detailed Documentation
HTML file editing support
This package contains support for editing HTML and XHTML inside a web page using the FCKeditor as a widget. This is a fairly simple application of FCKeditor, and simply instantiates a pre-configured editor for each widget. There are no options to control the editors individually.
In creating this, we ran into some limitations of the editor that are worth being aware of. Noting these as limitations does not mean that other editors do any better; what’s available seems to be a mixed bag.
The editor only deals with what can be contained inside a <body> element; anything that goes outside that, including the <body> and </body> tags, get lost or damaged. If there’s any way to configure FCKeditor to deal with such material, it isn’t documented.
There’s no real control of the HTML source; whitespace is not preserved as a programmer would expect. That’s acceptable in many use cases, but not all. Applications should avoid using this widget if the original whitespace must be maintained.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.i18n-3.8.0-2.lbn13.noarch
This package implements several APIs related to internationalization and
localization.
* Locale objects for all locales maintained by the ICU project.
* Gettext-based message catalogs for message strings.
* Locale discovery for Web-based requests.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.i18n-4.3.1-1.lbn25.noarch
This package implements several APIs related to internationalization and
localization.
* Locale objects for all locales maintained by the ICU project.
* Gettext-based message catalogs for message strings.
* Locale discovery for Web-based requests.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.i18n-4.3.1-1.lbn25.noarch
This package implements several APIs related to internationalization and
localization.
* Locale objects for all locales maintained by the ICU project.
* Gettext-based message catalogs for message strings.
* Locale discovery for Web-based requests.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.i18nmessageid-3.5.3-1.lbn13.armv6hl
To translate any text, we must be able to discover the source domain
of the text. A source domain is an identifier that identifies a
project that produces program source strings. Source strings occur as
literals in python programs, text in templates, and some text in XML
data. The project implies a source language and an application context.
We can think of a source domain as a collection of messages and
associated translation strings.
We often need to create unicode strings that will be displayed by
separate views. The view cannot translate the string without knowing
its source domain. A string or unicode literal carries no domain
information, therefore we use messages. Messages are unicode strings
which carry a translation source domain and possibly a default
translation. They are created by a message factory. The message factory
is created by calling MessageFactory with the source domain.
This package provides facilities for delaring such messages within
program source text; translation of the messages is the responsiblitiy of
the 'zope.i18n' package.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.i18nmessageid-3.5.3-1.lbn19.armv6hl
To translate any text, we must be able to discover the source domain
of the text. A source domain is an identifier that identifies a
project that produces program source strings. Source strings occur as
literals in python programs, text in templates, and some text in XML
data. The project implies a source language and an application context.
We can think of a source domain as a collection of messages and
associated translation strings.
We often need to create unicode strings that will be displayed by
separate views. The view cannot translate the string without knowing
its source domain. A string or unicode literal carries no domain
information, therefore we use messages. Messages are unicode strings
which carry a translation source domain and possibly a default
translation. They are created by a message factory. The message factory
is created by calling MessageFactory with the source domain.
This package provides facilities for delaring such messages within
program source text; translation of the messages is the responsiblitiy of
the 'zope.i18n' package.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
zope.i18nmessageid-3.5.3-1.lbn13.x86_64
To translate any text, we must be able to discover the source domain
of the text. A source domain is an identifier that identifies a
project that produces program source strings. Source strings occur as
literals in python programs, text in templates, and some text in XML
data. The project implies a source language and an application context.
We can think of a source domain as a collection of messages and
associated translation strings.
We often need to create unicode strings that will be displayed by
separate views. The view cannot translate the string without knowing
its source domain. A string or unicode literal carries no domain
information, therefore we use messages. Messages are unicode strings
which carry a translation source domain and possibly a default
translation. They are created by a message factory. The message factory
is created by calling MessageFactory with the source domain.
This package provides facilities for delaring such messages within
program source text; translation of the messages is the responsiblitiy of
the 'zope.i18n' package.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
zope.i18nmessageid-4.1.0-1.lbn25.py37.x86_64
To translate any text, we must be able to discover the source domain
of the text. A source domain is an identifier that identifies a
project that produces program source strings. Source strings occur as
literals in python programs, text in templates, and some text in XML
data. The project implies a source language and an application context.
We can think of a source domain as a collection of messages and
associated translation strings.
We often need to create unicode strings that will be displayed by
separate views. The view cannot translate the string without knowing
its source domain. A string or unicode literal carries no domain
information, therefore we use messages. Messages are unicode strings
which carry a translation source domain and possibly a default
translation. They are created by a message factory. The message factory
is created by calling MessageFactory with the source domain.
This package provides facilities for delaring such messages within
program source text; translation of the messages is the responsiblitiy of
the 'zope.i18n' package.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.i18nmessageid-4.1.0-1.lbn25.py37.x86_64
To translate any text, we must be able to discover the source domain
of the text. A source domain is an identifier that identifies a
project that produces program source strings. Source strings occur as
literals in python programs, text in templates, and some text in XML
data. The project implies a source language and an application context.
We can think of a source domain as a collection of messages and
associated translation strings.
We often need to create unicode strings that will be displayed by
separate views. The view cannot translate the string without knowing
its source domain. A string or unicode literal carries no domain
information, therefore we use messages. Messages are unicode strings
which carry a translation source domain and possibly a default
translation. They are created by a message factory. The message factory
is created by calling MessageFactory with the source domain.
This package provides facilities for delaring such messages within
program source text; translation of the messages is the responsiblitiy of
the 'zope.i18n' package.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
zope.i18nmessageid-4.0.3-1.lbn19.x86_64
To translate any text, we must be able to discover the source domain
of the text. A source domain is an identifier that identifies a
project that produces program source strings. Source strings occur as
literals in python programs, text in templates, and some text in XML
data. The project implies a source language and an application context.
We can think of a source domain as a collection of messages and
associated translation strings.
We often need to create unicode strings that will be displayed by
separate views. The view cannot translate the string without knowing
its source domain. A string or unicode literal carries no domain
information, therefore we use messages. Messages are unicode strings
which carry a translation source domain and possibly a default
translation. They are created by a message factory. The message factory
is created by calling MessageFactory with the source domain.
This package provides facilities for delaring such messages within
program source text; translation of the messages is the responsiblitiy of
the 'zope.i18n' package.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
