Home | Trees | Indices | Help |
---|
|
Remove special substrings from text.
Author: Chusslove Illich (Часлав Илић) <caslav.ilic@gmx.net>
License: GPLv3
Functions | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
(cat, msg, text) -> text
|
|
||
|
|||
(cat, msg, text) -> numerr
|
|
||
|
|||
(cat, msg, text) -> text
|
|
||
|
|||
(cat, msg, text) -> numerr
|
|
||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
(cat, msg, text) -> text
|
|
Variables | |
__package__ =
|
Function Details |
Remove accelerator marker from one of the text fields of the message [type F3A hook]. Accelerator marker is determined from the catalog, by calling its accelerator() method. Use set_accelerator() to set possible accelerator markers
after the catalog has been opened, in case it does not specify any on its
own. If catalog reports Accelerator marker can also be specified for a particular message, by
embedded # accelerator-marker: _ This overrides accelerator marker reported by the catalog.
See Also: pology.resolve.remove_accelerator |
Like remove_accel_text, except that if catalog reports
See Also: pology.resolve.remove_accelerator |
Remove accelerator marker from all applicable text fields in the message, as if remove_accel_text was applied to each [type F4A hook].
See Also: pology.resolve.remove_accelerator |
Like remove_accel_msg, except that if catalog reports
See Also: pology.resolve.remove_accelerator |
Remove markup from one of the text fields of the message [type F3A hook]. Expected markup types are determined from the catalog, by calling its
markup() method. Use set_markup() to set expected markup types after the
catalog has been opened, in case it does not specify any on its own. If
catalog reports
|
Remove markup from all applicable text fields in the message, as if remove_markup_text was applied to each [type F4A hook].
|
Remove format directives from one of the text fields of the message [type F3A hook]. The type of format directives is determined from message format flags.
See Also: pology.resolve.remove_fmtdirs |
Like remove_fmtdirs_text, except that each format directive is replaced by a non-whitespace "tick" instead of plainly removed [hook factory].
|
Remove format directives from all applicable text fields in the message, as if remove_fmtdirs_text was applied to each [type F4A hook].
|
Remove format directives from all applicable text fields in the message, as if remove_fmtdirs_text_tick was applied to each [hook factory].
|
Remove literal segments from one of the text fields of the message [type F3A hook]. Literal segments are URLs, email addresses, command line options, etc. anything symbolic that the machine, rather than human alone, should parse. Note format directives are excluded here, see remove_fmtdirs_text for removing them. By default, literals are removed heuristically, but this can be
influenced by embedded # literal-segment: foobar states that all # literal-segment: \w+bar # literal-segment: foo[&=] ### a sub comment To prevent any heuristic removal of literals, add a
See Also: pology.resolve.remove_literals |
Like remove_literals_text, except that each literal segment is replaced by a non-whitespace "tick" instead of plainly removed [hook factory].
|
Remove literal segments from all applicable text fields in the message, as if remove_literals_text was applied to each [type F4A hook].
|
Remove literal segments from all applicable text fields in the message, as if remove_literals_text_tick was applied to each [hook factory].
|
Remove literals by markup from one of the text fields of the message [type F3A hook]. An "intersection" of remove_markup_text and remove_literals_text, where literals segments are determined by markup, and both the segment text and its markup is removed. See documentation of these hooks for notes on what is considered literal and how markup type is determined.
|
Remove literal segments by markup from all applicable text fields in the message, as if remove_marlits_text was applied to each [type F4A hook].
|
Remove locally ignored entities from all applicable text fields in the message [type F4A hook]. Entities are ignored by listing them in the embedded
# ignore-entity: foobar, froobaz will remove entities
|
Rewrite parts of Translator comments may issue # rewrite-msgid: /foo/bar/ # rewrite-msgid: /foo (\w+) fam/bar \1 bam/ # rewrite-msgid: :foo/bar:foo/bam: If a search pattern is not valid, a warning on message is issued. Search pattern is case-sensitive.
|
Rewrite message by replacing all its elements with that of another
message which has the same Translator comments may issue # rewrite-inverse: # rewrite-inverse: Foo If the pattern does not match or it matches more than one other
message, current message is not touched; also if the pattern is left
empty and there is more than one other message. Search pattern is applied
to If more than one This hook is then executed again on the resulting message, in case the
new translator comments contain another
|
Remove all XML-like entities from original, and from translation all that are also found in original [type F4A hook]. To remove all entities from original, and all entitities from translation that also exist in original, may be useful prior to markup checks, when list of known entities is not available.
|
Like remove_paired_ents, except that each XML-like entity is replaced by a non-whitespace "tick" instead of plainly removed [hook factory].
|
Home | Trees | Indices | Help |
---|
Generated by Epydoc 3.0.1 on Thu Jul 24 21:00:27 2014 | http://epydoc.sourceforge.net |