Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

It turns out that some message texts already have parameter tokens for positional parameters provided in the code. In JSPUI localized message texts are inserted into the page using

...

fmt:message

...

tags, which may contain

...

fmt:param

...

tags to provide the positional parameters. To add named parameter substitution from the configuration, the proposed modification replaces these tags with

...

dspace:message

...

and

...

dspace:param

...

which have been added to the existing DSpace-specific tag library that is part of the product. This approach requires modifying all 150-odd JSP files which use message texts. The new parameter tokens have the form

...

{property.name

...

}

...

, where the string between the braces is the name of a property defined in the configuration.

XMLUI uses Cocoon's

...

i18n

...

facilities to look up localized message texts. Rather than try to replicate that rather extensive machinery, the proposed modification adds a new pipeline stage to each theme following the

...

i18n

...

transformation. A new transformer searches for

Code Block
<ds:cfg>

<ds:cfg> elements and replaces them with configuration property values. For example, to insert the value of

...

dspace.name.short

...

one would write

...

<ds:cfg

...

ds:key="dspace.name.short"/

...

>.