Questions about localization and more

Hi everyone!

I have few questions about localization and others:
1. How can I change the decimal separator and digit grouping symbol?
oxf.xforms.format.output.decimal only allows to set placement of
symbols, not those symbols itself.
2. What are the properties oxf.epilogue.xforms.preprocessing and
oxf.epilogue.xforms.preprocessing.uri for? I found them at the end of
standard XForms properties file:
https://github.com/orbeon/orbeon-forms/blob/master/src/resources-packaged/config/properties-xforms.xml
3. Is it safe to assume, that XForms fields that are not shown in
browser cannot be modified by user (using custom AJAX calls for
example)? Of course a form made with such assumption cannot be used with
client-side XForms plugins.

Regards,
Tambet



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Tambet,

> 1. How can I change the decimal separator and digit grouping symbol?
> oxf.xforms.format.output.decimal only allows to set placement of symbols,
> not those symbols itself.

IIRC format-number() uses default symbols. In XSLT, you also have
xsl:decimal-format which allows configuring the symbols used, but this
is missing in our implementation at the moment.

You might be able to work around this by using e.g.:

translate(format-decimal(), 'X', 'Y') where 'X' is the symbol produced
by format-decimal(), and 'Y' the one you actually want.

> 2. What are the properties oxf.epilogue.xforms.preprocessing and
> oxf.epilogue.xforms.preprocessing.uri for? I found them at the end of
> standard XForms properties file:
> https://github.com/orbeon/orbeon-forms/blob/master/src/resources-packaged/config/properties-xforms.xml

To implement a preprocessing pipeline or XSLT transformation on your
XForms page before it reaches the XForms engine.

> 3. Is it safe to assume, that XForms fields that are not shown in browser
> cannot be modified by user (using custom AJAX calls for example)? Of course
> a form made with such assumption cannot be used with client-side XForms
> plugins.

Only XForms controls that are relevant and not readonly can be
modified from the client. This is for security reasons, so that
someone can't inject values into an instance.

-Erik


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

On 11.12.2010 3:43, Erik Bruchez wrote: Thanks for a tip. Good decision to allow format properties as XPath
expression!

>> 2. What are the properties oxf.epilogue.xforms.preprocessing and
>> oxf.epilogue.xforms.preprocessing.uri for? I found them at the end of
>> standard XForms properties file:
>> https://github.com/orbeon/orbeon-forms/blob/master/src/resources-packaged/config/properties-xforms.xml
> To implement a preprocessing pipeline or XSLT transformation on your
> XForms page before it reaches the XForms engine.

So I set oxf.epilogue.xforms.preprocessing = true and
oxf.epilogue.xforms.preprocessing.uri to XSL stylesheet? And I can use
oxf: protocol to retrieve the stylesheet via resource manager? Can I
also use directory as URL, so all XSL stylesheets in that directory are
applied? Probably not.

Anyway, good to know, we implemented the same thing ourselves outside of
Orbeon. But we use several stylesheets and chain them together via
priorities.

>> 3. Is it safe to assume, that XForms fields that are not shown in browser
>> cannot be modified by user (using custom AJAX calls for example)? Of course
>> a form made with such assumption cannot be used with client-side XForms
>> plugins.
> Only XForms controls that are relevant and not readonly can be
> modified from the client. This is for security reasons, so that
> someone can't inject values into an instance.

Thanks, that simplifies our architecture a lot.

   Tambet


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

>> translate(format-decimal(), 'X', 'Y') where 'X' is the symbol produced
>> by format-decimal(), and 'Y' the one you actually want.
>
> Thanks for a tip. Good decision to allow format properties as XPath
> expression!

Yes :)

>> To implement a preprocessing pipeline or XSLT transformation on your
>> XForms page before it reaches the XForms engine.
>
> So I set oxf.epilogue.xforms.preprocessing = true and
> oxf.epilogue.xforms.preprocessing.uri to XSL stylesheet? And I can use oxf:
> protocol to retrieve the stylesheet via resource manager? Can I also use
> directory as URL, so all XSL stylesheets in that directory are applied?
> Probably not.

I checked and oxf.epilogue.xforms.preprocessing.uri only supports
pointing to an XPL at the moment:

http://goo.gl/2tPhN

There is even a nice TODO in there suggesting to support XSLT as well…

-Erik


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws