RE: [dev] empty MS Word text fields not empty in Writer
Hi Andrew, On 7. Juli 2010 14:01, Andrew Douglas Pitonyak wrote: > You are able to enumerate through your text fields and change the values in > those fields. > That would be easier than modifying OOo. Thanks for the advice, "createEnumeration" works fine on these fields as a workaround. But we have to build the OOo anyway, so changing the import filter is the best solution for us. > That said, this sounds like it may be a bug so you should probably file a bug > report as well. I agree with you, it's a bug, but we need a solution now. Regards Jörg Reschke - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] External dependencies and their parallel builds...
Hi, I'm now spending many CPU cycles on quite large machine (thanks Dave!) to beat 20 minutes of "build" time (in an already prepared build tree, starting with configure, bootstrap, build --all in instsetoo_native, one language, one packaging format, prebuilt mozilla, disabled binfilter). I'm working on some optimalizations together with others on #dev (football is not interesting anymore ;-). Building our external pre-requirements from the source is an issue. It is very ineffective :-( Caolan already reported issue #i107097# (http://qa.openoffice.org/issues/show_bug.cgi?id=107097). E.g. I was investigating why the build on 48 core machine spends 2 full minutes (120 seconds!) in the module curl to realize that the authors of curl are simply "genial". They are looking for the prototype of recvfrom with the code like this: for tryreturntype in 'type1' 'type2' 'type3' 'type4' for tryarg1 in 'type1' 'type2' 'type3' 'type4' for tryarg2 in 'type1' 'type2' 'type3' 'type4' ... compile, run the code well, recvfrom has 6 arguments and one return type... It takes AGES to test this. And they do so for recv, recvfrom, getnameinfo etc. Patching this out I was able to get down to 47 seconds there which is also very lng on such machine... This is simply terrible. I'm now walking over all modules to get this sorted out a bit. In many cases, we do not propagate -P value down to the source even when it is supported. I'll create patches for these cases. But there are harded cases like nss, openssl and python which are worth deeper investigation. Anyone interested to help with it? -- Pavel Janík - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Problems building DEV300_m84 on Windows with ccache
I am now trying to build the Windows build with ccache. I have followed the documentation here: http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows#ccache But I am getting this error: Entering /cygdrive/c/Backup/OpenOffice/DEV300_m84/soltools/mkdepend Compiling: soltools/mkdepend/Error: guw.pl: WinFormat: Not converted [-]X(=|:)/ type switch in :c:/PROGRA~1/MICROS~1.0/VC/bin/cl.exe:.Error: guw.pl: WinFormat: Not converted [-]X(=|:)/ type switch in :c:/Backup/OpenOffice/DEV300_m84/soltools/mkdepend/collectdircontent.cxx:.collectdircontent.cxx c:\backup\openoffice\dev300_m84\soltools\mkdepend\collectdircontent.hxx(6) : fatal error C1083: Cannot open include file: 'set': No such file or directory dmake: Error code 2, while making '../ wntmsci12.pro/obj/collectdircontent.obj' 1 module(s): soltools need(s) to be rebuilt Reason(s): Attention: if you fix the errors in above module(s) you may prolongue your the build issuing command: build --all:soltools dmake: Error code 1, while making 'build_instsetoo_native'
RE: [dev] Problems building DEV300_m83 on Windows.
Ok found out what the problem was. I was using "--disable-epm" in my
configure as documented for the Windows build some time ago, but apparently
is not required now.
> - - - - - - - - - Áframsendur póstur - - - - - - - - - -
> From: "Ramón García Fernández"
> To: "dev@openoffice.org"
> Date: Mon, 5 Jul 2010 15:53:05 +0200
> Subject: RE: [dev] Problems building DEV300_m83 on Windows.
> All I can say is that it works form me now. I have successfully built
> DEV300_m83 under Windows.
>
> -Mensaje original-
> De: Kristján Bjarni Guðmundsson [mailto:kristjanbja...@gmail.com]
> Enviado el: lunes, 05 de julio de 2010 0:42
> Para: dev@openoffice.org
> Asunto: Re: [dev] Problems building DEV300_m83 on Windows.
>
> I just tried DEV300_m84 and it is still broken with the same bug. Should I
> report this or has this already been fixed?
>
> Þann 29. júní 2010 09:13, skrifaði Kristján Bjarni Guðmundsson <
> kristjanbja...@gmail.com>:
>
> > I tried "build.pl verbose=true" in instsetoo_native but it only
> > returns the same error with no additional info. I also tried "dmake
> > util" but nothing happened (No output to console). I also tried
> > deleting everything (Including source) and starting the build from
> > scratch with only en-US but the same thing happens.
> >
> > The offending lines close to line 216 in the util/makefile.mk are:
> >
> > $(foreach,i,$(alllangiso) openofficewithjre_$i) :
> > $...@{$(PKGFORMAT:^".")} openofficewithjre_%{$(PKGFORMAT:^".")} :
> > $(PERL) -w $(SOLARENV)$/bin$/make_installer.pl -f
> > $(PRJ)$/util$/openoffice.lst -l $(subst,$(@:s/_/ /:1)_, $(@:b)) -p
> > OpenOffice_wJRE -u $(OUT) -buildid $(BUILD) -msitemplate
> > $(MSIOFFICETEMPLATEDIR) -msilanguage $(COMMONMISC)$/win_ulffiles
> > -format
> > $(@:e:s/.//) $(VERBOSESWITCH)
> >
> > Has anybody successfully build DEV300_m83 on Windows?
>
Re: [dev] empty MS Word text fields not empty in Writer
Hi Joerg, Le mercredi 07 juillet 2010 à 11:48 +0200, Joerg Reschke a écrit : > we have to migrate a lot of MS Word documents (.doc) to OOo and we have a > problem with the empty MS Word text fields. The Writer imports these text > fields, but the value is not empty: > - MS Word displays empty text fields as "°" and prints these values as > space. > - The Writer displays imported empty text fields with "@" and prints also > the value as "@". The support for these fields is evolving currently. A CWS has been integrated to prepare this, but there are still some incompatibilities to fix, mostly on the ODF front. I would be happy to see you join the effort ;) Regards, -- Cédric Bosdonnat Go-oo hacker http://go-oo.org OOo Eclipse Integration developer http://cedric.bosdonnat.free.fr - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Proposal of new project for UOF
Hi Li Heng, this is indeed good news. I'm sure, that will make OOo even more successful, especially in the Chinese market, of course. :-) Best regards, Peter LiHeng wrote: Hi ALL, UOF is a Chinese document format developed by Chinese government and all elements of UOF with Chinese tag-name and it is updated frequently in current period, a lots of new feature would be add into this standard. To launch a separate project of UOF may focus on special features of China and Chinese market, and all of office software provider who based on OpenOffice.org in China can maintain only one project of UOF interoperability for OpenOffice.org, and we can get the best interoperability of UOF in China. *There are 2 products, RedOffice& CS2C, based OpenOffice.org have supported UOF format. *And IBM Symphony has supported UOF too. *Several universities are also focus on UOF, OOXML and ODF converters. Proposal of UOF Interoperability Project Summary UOF is a Chinese developed open standard for 'office' applications. It includes word processing, presentation, and spreadsheet modules, and is made up of GUI, API, and format specifications. The document format described uses XML contained in a compressed file container. This project improve the interoperability of UOF, include all features, GUI and API and solve the problems in Chinese office application system. UOF is not in same structure of ODF, some features(such as Media Object and Conditional format of Spreadsheet ) can not transform well only with XSLT, so we need to develop a set of extensions to transform them into a friendly structure first. For UOF API we must bind a bundle of interfaces and services on OpenOffice.org in order to OpenOffice.org can be integrated into office system with UOF API. The mission of this project is improving the interoperability of UOF.We're going in for transforming the format between UOF and ODF with XSLT.There's an UOF filter including an extension to solve some very important problems with Calc and OLE. Scope 1.To develop and maintain the filters for every UOF version. Include XSLT template and a set extensions. 2.To develop and maintain all IDL and services of UOF APIs 3.To Implement the Chinese special features of UOF in OpenOffice.org 4.To collect the suggestions on UOF from community and participate in editing of UOF We will open all XSLT and filter(now as a extension) source code we have done. And to work on new version of UOF with all contributors. Now we are working on transforming the format between UOF2.0 and ODF with XSLT stylesheet, and the new features about media object. UOF2.0 is multiple documents construction and will be a kind of compression format. Each document is a XML file using Chinese tags. We should convert all documents into a FlatXML which could present all tags of different documents,and then convert the FlatXML file into ODF with XSLT stylesheet. And in the other conversion direction ,firstly,ODF will be converted into multiple documents with XSLT stylesheet,and then the multiple documents will be packed into UOF2.0 format. Best regards! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: What is the best desktop tool to browse/navigate the OOo source?
Am Thu, 08 Jul 2010 10:15:58 +0700 schrieb Samphan Raruenrom : > Thank you :) Hi Samphan, more development resources are here: http://wiki.services.openoffice.org/wiki/Development if you feel something missing, let us know! BR, Bjoern - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Proposal of new project for UOF
+1 I think the UOF project will strengthen the OOo adoption in the Chinese market. - Dieter On 07.07.10 08:03, LiHeng wrote: Hi ALL, UOF is a Chinese document format developed by Chinese government and all elements of UOF with Chinese tag-name and it is updated frequently in current period, a lots of new feature would be add into this standard. To launch a separate project of UOF may focus on special features of China and Chinese market, and all of office software provider who based on OpenOffice.org in China can maintain only one project of UOF interoperability for OpenOffice.org, and we can get the best interoperability of UOF in China. *There are 2 products, RedOffice& CS2C, based OpenOffice.org have supported UOF format. *And IBM Symphony has supported UOF too. *Several universities are also focus on UOF, OOXML and ODF converters. Proposal of UOF Interoperability Project Summary UOF is a Chinese developed open standard for 'office' applications. It includes word processing, presentation, and spreadsheet modules, and is made up of GUI, API, and format specifications. The document format described uses XML contained in a compressed file container. This project improve the interoperability of UOF, include all features, GUI and API and solve the problems in Chinese office application system. UOF is not in same structure of ODF, some features(such as Media Object and Conditional format of Spreadsheet ) can not transform well only with XSLT, so we need to develop a set of extensions to transform them into a friendly structure first. For UOF API we must bind a bundle of interfaces and services on OpenOffice.org in order to OpenOffice.org can be integrated into office system with UOF API. The mission of this project is improving the interoperability of UOF.We're going in for transforming the format between UOF and ODF with XSLT.There's an UOF filter including an extension to solve some very important problems with Calc and OLE. Scope 1.To develop and maintain the filters for every UOF version. Include XSLT template and a set extensions. 2.To develop and maintain all IDL and services of UOF APIs 3.To Implement the Chinese special features of UOF in OpenOffice.org 4.To collect the suggestions on UOF from community and participate in editing of UOF We will open all XSLT and filter(now as a extension) source code we have done. And to work on new version of UOF with all contributors. Now we are working on transforming the format between UOF2.0 and ODF with XSLT stylesheet, and the new features about media object. UOF2.0 is multiple documents construction and will be a kind of compression format. Each document is a XML file using Chinese tags. We should convert all documents into a FlatXML which could present all tags of different documents,and then convert the FlatXML file into ODF with XSLT stylesheet. And in the other conversion direction ,firstly,ODF will be converted into multiple documents with XSLT stylesheet,and then the multiple documents will be packed into UOF2.0 format. Best regards! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
