R12 PO Upgrade Recommendations : Multilingual strategy in PO Output for Communications Forms
We have been discussing the best strategy for multilingual support in the BiPublisher based xsl-fo PO forms used in the PO Output for Communications. Presently we see a few possible strategies:
1. Single, Message Table Based Template Strategy:
Oracle uses the Fnd.Messages table to store all non-data text displayed on the forms. Upon print, fax, email, etc, it will use the selected language, and merge labels and data onto a single template.
2. Mixed, Message Table Based Template Strategy:
One could use the Fnd.Messages strategy in step 1 above, but deploy separate templates for any language that does not fit the main template.