[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Java guru's around?

From: Daniel Barbato <catch_at_unidentified.org>
Date: 2005-04-05 11:39:00 CEST

Hi Steve,

I hope you don't mind me posting a reply to this off the thread. I was
wondering if there had been any take up on this. If not I wouldn't mind
having a stab at it. I've been using open source for long enough now,
time I started putting something back in. I don't have time at the
moment to look at it, got a major deadline in work, and a website that I
need to crack on with, however if you can wait a month or so before
someone starts looking at this I wouldn't mind flexing my fingers.



SteveKing wrote:

> Hi,
> Some days ago, Lübbe suggested to use the KDE way of translating our
> docs. The problem is though, the tool KDE uses to extract the strings
> to translate from the docbook sources only runs on *NIX, not on Windows.
> I've had a look at the sources here:
> http://webcvs.kde.org/kdesdk/poxml/#dirlist
> it's not very complicated, if you have a decent xml library at hand.
> So my question is: are there any java guru's out there who would like
> to create such a tool? AFAIK java has xml already built in, so it
> wouldn't be too much work.
> The tool would have to do:
> - take a docbook xml file, extract all strings which need translating,
> write those strings to a pot file.
> - take a po file and a docbook xml file, replace all strings in the
> xml file with the translated strings of the po file and write the
> translated xml file somewhere.
> any volunteers?
> (of course, if you like you can use any programming language which
> also runs on windows).
> Stefan

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Apr 5 11:39:29 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.