[dev] Re: Problems downloading source through Mercurial
Hi Seth, I'm not sure what you are trying to achieve. OOo should have PyUno and - if it is a build provided by Oracle - its own version of Python and both should fit to each other. Admittedly I'm not completely sure about that, if you have bad luck, even the Oracle builds didn't contain an own Python. But if you build OOo by yourself, you should be able to make sure that OOo's own copy of Python is used in the build (and thus put into the installation set) and not the version of the system. See what configure offers you with regard to Python. Regards, Mathias Am 10.10.2011 05:41, schrieb Seth Shich: HI Mathias, Thanks for the information. Perhaps, I should tell you why I want to build OOo, and, then, maybe you could suggest what course I should take. I am trying to get PyUno working so that I can read and interface with .doc and .docx files (e.g. highlight certain words in documents, such as proper names) while they are being viewed by users in MsWord. The problem is that PyUno links against Python2.3 and, therefore, I cannot run it on Mac OS X 10.7.1: 10.7.1 does not have Python2.3 in its complete form, and, at any rate, I wouldn't want to use that Python version because it would prevent imports of other modules requiring later Python versions. PyUno, then, must be made to link against either Python 2.6.7 or Python 2.7, the Python versions I have on my system. But, how to do this? I read here, at http://www.mail-archive.com/mac@porting.openoffice.org/msg03582.html, that: Those who build OOo by themselves will be able to just use --with[out]-system-python, but only very, very few Mac users will build their own copy of OOo. Thus it is important to decide on the default, what the installsets offered from www.openoffice.org will include (or not include) At this stage, I have downloaded the entire repository for OOo. Is there a way to selectively build just the PyUno Module? Also, do you have any suggestions as to where I can begin? I am a newbie and am becoming somewhat overwhelmed at what has become quite a daunting task. Thanks, in advance, for any help you can provide. Sincerely, Seth BTW: building OOo on Mac OS X 10.7 is not easy. It doesn't work out of the box. You have at least to back to the 10.4 SDK and XCode 3.2.6. Please see the discussion here: http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201109.mbox/%3ce0296709-0cf0-4494-a518-e11f32e74...@herrmannsdorfer.de%3e Regards, Mathias -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help
[dev] Re: Problems downloading source through Mercurial
What I can't figure out from the use case is why isn't Seth developing a plug-in for Microsoft Word if it is about Word documents and Microsoft Word is being used to view the document already? So, what else is there to the use case that would make it clear why code from OO.o is needed? - Dennis E. Hamilton tools for document interoperability, http://nfoWorks.org/ dennis.hamil...@acm.org gsm: +1-206-779-9430 @orcmid -Original Message- From: Mathias Bauer [mailto:nospamfor...@gmx.de] Sent: Monday, October 10, 2011 14:27 To: dev@openoffice.org Subject: [dev] Re: Problems downloading source through Mercurial Hi Seth, I'm not sure what you are trying to achieve. OOo should have PyUno and - if it is a build provided by Oracle - its own version of Python and both should fit to each other. Admittedly I'm not completely sure about that, if you have bad luck, even the Oracle builds didn't contain an own Python. But if you build OOo by yourself, you should be able to make sure that OOo's own copy of Python is used in the build (and thus put into the installation set) and not the version of the system. See what configure offers you with regard to Python. Regards, Mathias Am 10.10.2011 05:41, schrieb Seth Shich: HI Mathias, Thanks for the information. Perhaps, I should tell you why I want to build OOo, and, then, maybe you could suggest what course I should take. I am trying to get PyUno working so that I can read and interface with .doc and .docx files (e.g. highlight certain words in documents, such as proper names) while they are being viewed by users in MsWord. The problem is that PyUno links against Python2.3 and, therefore, I cannot run it on Mac OS X 10.7.1: 10.7.1 does not have Python2.3 in its complete form, and, at any rate, I wouldn't want to use that Python version because it would prevent imports of other modules requiring later Python versions. PyUno, then, must be made to link against either Python 2.6.7 or Python 2.7, the Python versions I have on my system. But, how to do this? I read here, at http://www.mail-archive.com/mac@porting.openoffice.org/msg03582.html, that: Those who build OOo by themselves will be able to just use --with[out]-system-python, but only very, very few Mac users will build their own copy of OOo. Thus it is important to decide on the default, what the installsets offered from www.openoffice.org will include (or not include) At this stage, I have downloaded the entire repository for OOo. Is there a way to selectively build just the PyUno Module? Also, do you have any suggestions as to where I can begin? I am a newbie and am becoming somewhat overwhelmed at what has become quite a daunting task. Thanks, in advance, for any help you can provide. Sincerely, Seth BTW: building OOo on Mac OS X 10.7 is not easy. It doesn't work out of the box. You have at least to back to the 10.4 SDK and XCode 3.2.6. Please see the discussion here: http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201109.mbox/%3ce0296709-0cf0-4494-a518-e11f32e74...@herrmannsdorfer.de%3e Regards, Mathias -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help
[dev] Re: Problems downloading source through Mercurial
I was under the impression that I could use OOo's PyUno to read and manipulate .doc and .docx files from Python and even to interact with those files while they are opened. Is this not correct? If it is, I would prefer to use Python because of its natural language processing capabilities (e.g. NLTK). Also, if I can avoid having to spend between $600 and $1,000 to read .doc and .docx through Microsoft Visual Studio, I would certainly prefer to do so. From: dennis.hamil...@acm.org To: dev@openoffice.org CC: sethsh...@hotmail.com Date: Mon, 10 Oct 2011 15:08:18 -0700 Subject: [dev] Re: Problems downloading source through Mercurial What I can't figure out from the use case is why isn't Seth developing a plug-in for Microsoft Word if it is about Word documents and Microsoft Word is being used to view the document already? So, what else is there to the use case that would make it clear why code from OO.o is needed? - Dennis E. Hamilton tools for document interoperability, http://nfoWorks.org/ dennis.hamil...@acm.org gsm: +1-206-779-9430 @orcmid -Original Message- From: Mathias Bauer [mailto:nospamfor...@gmx.de] Sent: Monday, October 10, 2011 14:27 To: dev@openoffice.org Subject: [dev] Re: Problems downloading source through Mercurial Hi Seth, I'm not sure what you are trying to achieve. OOo should have PyUno and - if it is a build provided by Oracle - its own version of Python and both should fit to each other. Admittedly I'm not completely sure about that, if you have bad luck, even the Oracle builds didn't contain an own Python. But if you build OOo by yourself, you should be able to make sure that OOo's own copy of Python is used in the build (and thus put into the installation set) and not the version of the system. See what configure offers you with regard to Python. Regards, Mathias Am 10.10.2011 05:41, schrieb Seth Shich: HI Mathias, Thanks for the information. Perhaps, I should tell you why I want to build OOo, and, then, maybe you could suggest what course I should take. I am trying to get PyUno working so that I can read and interface with .doc and .docx files (e.g. highlight certain words in documents, such as proper names) while they are being viewed by users in MsWord. The problem is that PyUno links against Python2.3 and, therefore, I cannot run it on Mac OS X 10.7.1: 10.7.1 does not have Python2.3 in its complete form, and, at any rate, I wouldn't want to use that Python version because it would prevent imports of other modules requiring later Python versions. PyUno, then, must be made to link against either Python 2.6.7 or Python 2.7, the Python versions I have on my system. But, how to do this? I read here, at http://www.mail-archive.com/mac@porting.openoffice.org/msg03582.html, that: Those who build OOo by themselves will be able to just use --with[out]-system-python, but only very, very few Mac users will build their own copy of OOo. Thus it is important to decide on the default, what the installsets offered from www.openoffice.org will include (or not include) At this stage, I have downloaded the entire repository for OOo. Is there a way to selectively build just the PyUno Module? Also, do you have any suggestions as to where I can begin? I am a newbie and am becoming somewhat overwhelmed at what has become quite a daunting task. Thanks, in advance, for any help you can provide. Sincerely, Seth BTW: building OOo on Mac OS X 10.7 is not easy. It doesn't work out of the box. You have at least to back to the 10.4 SDK and XCode 3.2.6. Please see the discussion here: http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201109.mbox/%3ce0296709-0cf0-4494-a518-e11f32e74...@herrmannsdorfer.de%3e Regards, Mathias -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@openoffice.org For additional commands send email to sy...@openoffice.org with Subject: help
