On 3 Jul 2009, at 01:21, Laura Bailey wrote:
> Sorry for the late reply - this was buried in my inbox.
>
> Pete, I have no idea - asking around, there's some concern about the
> way Maven uses po/pot files, since we tend to use Publican. I'm
> afraid I have no idea how to go about automating the process.
We still use Publican to update the PO/POT, the maven-jdocbook-plugin
is just for processing the translations (via a call to po2xml) and
then launching docbook etc.
So, it should just be a publican job that can svn update, run make
update-po-all, svn add -f *, svn commit - the environments I have
access to set up such jobs don't have Publican installed.
>
> Pete Muir wrote:
>>
>> On 21 Jun 2009, at 12:14,
denis.forveille@... wrote:
>>
>>> I've corrected a minor bug in the seam reference guide
>>> (JBSEAM-4256).
>>> For this I updated and committed the file named "doc/
>>> Seam_Reference_Guide/en-US/I18n.xml"
>>> Q:
>>> - do I have to do something extra (update/generate/commit/?) to
>>> cope with the corresponding "I18n.po" files for the other locales?
>>> - or is it the build (or someone/something else) that will update/
>>> generate/commit those files?
>>
>> This is supposed to be a service that is provided by "something
>> else" :-)
>>
>> Laura, this (automatic, weekly regeneration of po/pot files) is
>> something Samson said he could get set up for us. Can you help with
>> this?
>>
>> pete
>
> --
> Laura Bailey
> Engineering Content Services
> Red Hat - Brisbane, Australia
> IRC: laubai
>
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev
