Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There's nothing to add to Stefan's and Sven's answers, at least not in regards to the technical side of your question. I wonder however whether your basic approach to the problem couldn't be a different one: </p> <p>Assuming that your application is mainly based on an Xpages frontend design I wonder what a LS agent could deliver to your users that needs to be translated. Maybe some mail content, or some field content printed into documents using backend classes. In both cases, however, you wouldn't have any chance using any localization parameters that come from either client preferences or from user preferences stored in user profiles or something like that: scheduled agents simply cannot react to those settings. What I want to say is: are you really sure that your LS code in fact needs to access translated strings? Or wouldn't it be easier to put that load onto SSJS code that in turn can access your resource bundles?</p> <p>And yet another thought: I really like the Xpages' approach in using i18n, but there's always the drawback that you need a designer client to apply translations, and in same cases the database owner needs simple access to the translation sheets but doens't have the menas or the access rights to use Domino Designer. Therefor at least in some applications I prefer to use sets of config documents stored in the database itself, to be accessed by all kinds of codes, although I'm aware that this might impose a performance issue. So maybe Stefan's idea of using the server's file system for that could be a nice solution to that.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload