- pcsInnerConfigID :: PCLT_InnerConfigID
-
- pcsCompositePlaceholderWrapper :: ByteString
Symbols sequence denoting wrapping parentheses (identical
for both - openning ang closing), that are to be put
around *composite* name in a template text.
- pcsParameterPlaceholderWrapper :: ByteString
Symbols sequence denoting wrapping parentheses (identical
for both - openning ang closing), that are to be put
around *parameter* name in a template text.
- pcsInsuficientDetLevelPlaceholder :: ByteString
For case, when representation reciever uses detalization
level, that isn't enough to meet requirement specified by
the template (from which representation was to be made):
symbols sequence, that PCLT engine must place
instead of content from template/composite.
- pcsMarkingErrorPlaceholderWrapper :: ByteString
Symbols sequence denoting wrapping parentheses (identical
for both - openning ang closing), that are to be put
(by PCLT engine) in representation, where it failed to
make a proper representation from a template piece
(composite or parameter).
- pcsDefaultLanguage :: LanguageName
Catalog default (primary) language.
- pcsStrictOrient_ofParamsAndCmpsts_onDfltLngTplsSets :: StrictOrient_ofParamsAndCmpsts_onDfltLngTplsSets
Object:
- Should all localizations of template be strictly oriented
on localization in default (primary) language? (in case of
such orientation, NO template localized in a nondefault
language is allowed to have sets of composites and
parameters different from ones specified for template
localization in the default language)
- Exclusions - when not to be strict with templates
structures, - if strictness is on;
or when to be strict, - if strictness is off.
- pcsAllowUntemplatedMessages :: Bool
Is it allowed to demand representations from catalog, when
referenced template/composite ID isn't known in given
catalog?
In case, if allowed, on place of unknown composite
the engine (when making representation) will simply put
it's (unknown) ID (given that recievers detailization level
statisfies a requirement: it must be maximal (infinitely
big)), followed by (if enabled by other config parameter)
all the parameters used by current instaniation.
- pcsAllowUntemplatedLocalizationsOfMessages :: Bool
Is it allowed to demand representations from catalog, when
referenced template/composite ID is persistent in catalog,
but not in representation language?
In case, if allowed, on place of unknown composite
the engine (when making representation) will simply put
it's (unknown) ID (given that recievers detailization level
statisfies a requirement: it must be maximal (infinitely
big)), followed by (if enabled by other config parameter)
all the parameters used by current instaniation.
- pcsShowAdhocParamsInResultOfUntemplated :: Bool
If it's allowed to require representation of
a template/composite (or it's localisation), that is absent
in catalog then (given that reciever's detailization level
statisfies a requirement: it must be maximal (infinitely
big)) together with it's (unknown composite) ID:
should there also be put all the parameters (array of
name:value pairs), used by current instaniation?
- pcsInstaniationResultMaxSize :: Int64
DEFAULT maximal allowed size of representation resulting from
instaniation of a single PCSI. If user gives on the input
his ConstraintedLBS with different constraint on size, then his
constraint is used instead.
- pcsAllowEmptySDL_parseItByModusMargin :: Bool
Is it allowed to give an empty value to the field
"representation detailization level" (Text.PCLT.SDL)?
If allowed, then it's value will be chosen automatically
by the margin
depending on modus: maximal ("+inf") in case, when it's a
requirement by a template, or minimal ("zero"), when it's
an assigment to a reciever of representation
- pcsAllowUnreadableSDL_parseIdByModusMargin :: Bool
Is it allowed to give an unreadable value to the field
"representation detailization level" (Text.PCLT.SDL)?
If allowed,
then it's value will be chosen automatically by the margin
depending on modus: maximal ("+inf") in case, when it's a
requirement by a template, or minimal ("zero"), when it's
an assigment to a reciever of representation
- pcsAllowFailureToDetermineSDL_parseIdByModusMargin :: Bool
If pcsi2text
(Text.PCLT.MakeMessage) function fails to
determine an SDL requiered by used template (due to
referential cycle, missing referenced template,
PCLT_SDL_Errornous
or other reason) - should this failure
lead to absolute denial to represent problem template, or
should the pcsi2text
treat it like "+inf"
(PCLT_SDL InfinitelyBig_SDL
)? The error will be returned
anyway, but question is purely about output representation.
- pcsNewlineLBS :: ByteString
Sequence of symbols used, when representing a specialcase
of parameter value - Newline_PV
(Text.PCLT.PCSI).
(Different OSes use different newline strings: in Linux it's
#10, in M$ - #13#10, MacOS - #13)
- pcsReparsingDepthMax :: ReparsingDepth
NOT USED, RESERVED FOR FUTURE VERSIONS OF PCLT!
Maximal allowed depth of reparsing.
- pcsReparseParameterContentMaxSize :: Int64
NOT USED, RESERVED FOR FUTURE VERSIONS OF PCLT!
Maximal allowed size of representation resuling from
instaniating a reparsing result.