On 5/11/2012 9:57 AM, Jacques Le Roux wrote:
From: "Jacopo Cappellato" <[email protected]>
On May 11, 2012, at 9:55 AM, Jacques Le Roux wrote:
This makes sense Scott! We could even link the help from wiki
online for demos. The problem is we use Confluence and its export
is known to be flawed and not supported/mantained anymore.
That is not related to what Scott was saying: the Confluence
autoexport is related to the ability to transform a Confluence page
into a static html page.
I think it can be continued this way in the meantime.
I disagree that we should continue to add incomplete stuff to the
trunk (and release branches) until a better design is in place.
This will not stop the huge effort of creating documentation and
actual content for the help screens: contributors can do this in
Confluence (or similar) and then, when we will have defined a good
design it will be easy to write a script to import the content
into the new format.
How to handle i18n automatisation in Confluence? Though yes, it's not
really automated in online help as well, since we need to
create as much files as languages.
The approach I use is to include the help URLs in the UI label files -
so each translation can have its own URL. The URLs can point to content
generated within OFBiz, or to an external site.
-Adrian
