Re: Calling all consultants, developers, trainers, etc., offering professional services related to OpenOffice

[Andrea Pescetti <pe...@apache.org>]

On 04/10/2012 Rob Weir wrote:
> We're in the process of creating an updated OpenOffice professional
> services directory, to replace the outdated one that we removed from
> the website a few months ago.

I've been looking at doing the same for the "/it" website, with the aim 
to obtain a list of Italian consultants. As I see it, this would be a 
"fork" of the consultants database, since we would list there only the 
Italian consultants (as it used to be) and link to
http://www.openoffice.org/bizdev/consultants.html
for global information.

The problem is that in this case we will want the output page to appear 
under "/it" and take the branding normally applied to the "/it" directory.

What's the best way to do it? An "svn copy" of "consultants" from 
"/bizdev" to "/it" and subsequent customization? This is not so nice, 
but with version control it wouldn't be very painful to synchronize 
relevant changes. Or shall I need to just put in "/bizdev/consultants" a 
new file, say "to-html_it.xsl", that takes a new database, say 
"consultants_it.xml", and produces an HTML file in "/it"? The latter 
option reduces duplication but adds clutter to "/bizdev/consultants".

Regards,
   Andrea.

Re: Calling all consultants, developers, trainers, etc., offering professional services related to OpenOffice

[Rob Weir <ro...@apache.org>]

On Mon, Nov 19, 2012 at 6:00 PM, Andrea Pescetti <pe...@apache.org> wrote:
> On 04/10/2012 Rob Weir wrote:
>>
>> We're in the process of creating an updated OpenOffice professional
>> services directory, to replace the outdated one that we removed from
>> the website a few months ago.
>
>
> I've been looking at doing the same for the "/it" website, with the aim to
> obtain a list of Italian consultants. As I see it, this would be a "fork" of
> the consultants database, since we would list there only the Italian
> consultants (as it used to be) and link to
> http://www.openoffice.org/bizdev/consultants.html
> for global information.
>
> The problem is that in this case we will want the output page to appear
> under "/it" and take the branding normally applied to the "/it" directory.
>
> What's the best way to do it? An "svn copy" of "consultants" from "/bizdev"
> to "/it" and subsequent customization? This is not so nice, but with version
> control it wouldn't be very painful to synchronize relevant changes. Or
> shall I need to just put in "/bizdev/consultants" a new file, say
> "to-html_it.xsl", that takes a new database, say "consultants_it.xml", and
> produces an HTML file in "/it"? The latter option reduces duplication but
> adds clutter to "/bizdev/consultants".
>

Currently we have no Italian consultants listed here:
http://www.openoffice.org/bizdev/consultants.html

If we can avoid maintaining separate lists, it is probably best.

Here are some things that could be done by using the single
consultants.xml and enhancing the XSLT:

1) Produce separate HTML's for different languages, with the table
headers translated.  (This is already working)

2) We could allow multiple <description> fields per consultant for
translations, e.g., <description lang="it">.  We could then use the
translated versions when we generate locale-specific HTML output files.

But there is the complexity of language != country.  Currently we're
encoding countries that the consultant does business in.  In some
cases, like Belgium, we cannot make a language assumption based on
that.

-Rob

> Regards,
>   Andrea.