Re: [announce] genLang extract is ready.

On 8/31/13, janI wrote: > Hi > > I am pleased to inform you, that I have reached a major milestone with > genLang. > > genLang is now integrated in the build system (for extraction), and I have > carefully tested that "genLang extract" (generation of .pot template files) > is 100% identical to th

Re: [announce] genLang extract is ready.

On 16/09/2013 janI wrote: Now I have removed all warnings, so this is now one of the few modules without warnings (actually that would be a good task for a new developer). R1523556 compiles without warnings on ubuntu 12.04 and windows7 (VC2012). I now retried on the same Fedora 19 machine and i

Re: [announce] genLang extract is ready.

On 16 September 2013 00:46, Andrea Pescetti wrote: > On 15/09/2013 janI wrote: > > On 15 September 2013 00:49, janI wrote: >> >>> Please correct me, but fedora 19 is not part of our product release ? my >>> aim is to support what AOO supports. >>> >> > It is a standard Linux system, and OpenOffi

Re: [announce] genLang extract is ready.

On 16 September 2013 00:34, Ariel Constenla-Haile wrote: > On Sun, Sep 15, 2013 at 03:28:06PM +0200, janI wrote: > > I have investigated a bit further: > > > > At the top of gCon.cxx you find: > > > > #ifdef _WIN32 #include #include #define > > OS_ACCESS(x,y) _access(x,y) #define OS_MKDIR(x) _mk

Re: [announce] genLang extract is ready.

On 15/09/2013 janI wrote: On 15 September 2013 00:49, janI wrote: Please correct me, but fedora 19 is not part of our product release ? my aim is to support what AOO supports. It is a standard Linux system, and OpenOffice should build and run on all recent Linux systems. For sure it would be

Re: [announce] genLang extract is ready.

On Sun, Sep 15, 2013 at 03:28:06PM +0200, janI wrote: > I have investigated a bit further: > > At the top of gCon.cxx you find: > > #ifdef _WIN32 #include #include #define > OS_ACCESS(x,y) _access(x,y) #define OS_MKDIR(x) _mkdir(x) #else > #include #include #define OS_ACCESS(x,y) > access(x,y

Re: [announce] genLang extract is ready.

On 15 September 2013 00:49, janI wrote: > > > > On 15 September 2013 00:35, Andrea Pescetti wrote: > >> On 15/09/2013 janI wrote: >> >>> Thanks for trying it, please suply more information about your setup so I >>> can determine the problem. >>> >> >> Sure. That particular build is done on a Fed

Re: [announce] genLang extract is ready.

On 15 September 2013 00:35, Andrea Pescetti wrote: > On 15/09/2013 janI wrote: > >> Thanks for trying it, please suply more information about your setup so I >> can determine the problem. >> > > Sure. That particular build is done on a Fedora 19 Linux system that I use > to test building with new

Re: [announce] genLang extract is ready.

On 15/09/2013 janI wrote: Thanks for trying it, please suply more information about your setup so I can determine the problem. Sure. That particular build is done on a Fedora 19 Linux system that I use to test building with newer compilers/tools, and that builds trunk correctly. No cross-comp

Re: [announce] genLang extract is ready.

On 14 September 2013 21:32, Andrea Pescetti wrote: > On 31/08/2013 janI wrote: > >> I am pleased to inform you, that I have reached a major milestone with >> genLang. >> > > Thanks a lot for the achievement. I'm quite enthusiastic about it, but I > waited to comment until I could play a bit with

Re: [announce] genLang extract is ready.

On 31/08/2013 janI wrote: I am pleased to inform you, that I have reached a major milestone with genLang. Thanks a lot for the achievement. I'm quite enthusiastic about it, but I waited to comment until I could play a bit with it. 1) run "build --all --genPO" or "build --genPO" Unfortunat

Re: [announce] genLang extract is ready.

On Sep 3, 2013 7:16 PM, "Tsutomu Uchino" wrote: > > Hi, > > I have the same problem on ja locale. > I downloaded PO files from the Pootle getLang project. These files contains > correct strings in UTF-8. > But their header contains the following line: > > "Content-Type: text/plain; charset=iso-885

Re: [announce] genLang extract is ready.

Hi, I have the same problem on ja locale. I downloaded PO files from the Pootle getLang project. These files contains correct strings in UTF-8. But their header contains the following line: > "Content-Type: text/plain; charset=iso-8859-1\n" Is it used to detect the file encoding? Another project f

Re: [announce] genLang extract is ready.

On 3 September 2013 10:37, Herbert Duerr wrote: > On 02.09.2013 20:03, Regina Henschel wrote: > >> 2) I see a coding problem for umlauts, for example >> https://translate.apache.org/**de/aooGenLang4/chart2.po/** >> translate/#unit=20600974

Re: [announce] genLang extract is ready.

On 02.09.2013 20:03, Regina Henschel wrote: 2) I see a coding problem for umlauts, for example https://translate.apache.org/de/aooGenLang4/chart2.po/translate/#unit=20600974 This might be an encoding problem: In the browser the text shows as "Bereich für %VALUETYPE" which is the correct UTF-8

Re: [announce] genLang extract is ready.

On 2 September 2013 22:03, Ricardo Berlasso wrote: > 2013/9/2 janI > > > On 2 September 2013 20:03, Regina Henschel > > wrote: > > > > > Hi Jan, > > > > > > I have seen, that there is a new project "Apache OpenOffice genLang" on > > > Pootle and had a look into it for German. > > > > > > 1) I s

Re: [announce] genLang extract is ready.

2013/9/2 janI > On 2 September 2013 20:03, Regina Henschel > wrote: > > > Hi Jan, > > > > I have seen, that there is a new project "Apache OpenOffice genLang" on > > Pootle and had a look into it for German. > > > > 1) I see, that there is a difference in the way file and location is > > divided

Re: [announce] genLang extract is ready.

On 2 September 2013 20:03, Regina Henschel wrote: > Hi Jan, > > I have seen, that there is a new project "Apache OpenOffice genLang" on > Pootle and had a look into it for German. > > 1) I see, that there is a difference in the way file and location is > divided compared to the current projects.

Re: [announce] genLang extract is ready.

Hi Jan, I have seen, that there is a new project "Apache OpenOffice genLang" on Pootle and had a look into it for German. 1) I see, that there is a difference in the way file and location is divided compared to the current projects. Is this intended? 2) I see a coding problem for umlauts, f

Re: [announce] genLang extract is ready.

On 9/1/13 4:03 PM, Rob Weir wrote: > On Sat, Aug 31, 2013 at 1:07 PM, janI wrote: >> Hi >> >> I am pleased to inform you, that I have reached a major milestone with >> genLang. >> >> genLang is now integrated in the build system (for extraction), and I have >> carefully tested that "genLang extra

Re: [announce] genLang extract is ready.

On Sat, Aug 31, 2013 at 1:07 PM, janI wrote: > Hi > > I am pleased to inform you, that I have reached a major milestone with > genLang. > > genLang is now integrated in the build system (for extraction), and I have > carefully tested that "genLang extract" (generation of .pot template files) > is

Re: [announce] genLang extract is ready.

On Aug 31, 2013 10:07 AM, "janI" wrote: > > Hi > > I am pleased to inform you, that I have reached a major milestone with > genLang. > > genLang is now integrated in the build system (for extraction), and I have > carefully tested that "genLang extract" (generation of .pot template files) > is 10

Re: [announce] genLang extract is ready.

Very cool! Great work Jan! On Aug 31, 2013, at 10:07 AM, janI wrote: > Hi > > I am pleased to inform you, that I have reached a major milestone with > genLang. > > genLang is now integrated in the build system (for extraction), and I have > carefully tested that "genLang extract" (generation o

[announce] genLang extract is ready.

Hi I am pleased to inform you, that I have reached a major milestone with genLang. genLang is now integrated in the build system (for extraction), and I have carefully tested that "genLang extract" (generation of .pot template files) is 100% identical to the existing system (except for the appro