writer2latex_0.5.0.2-1_amd64.changes ACCEPTED

Accepted: libwriter2latex-java-doc_0.5.0.2-1_all.deb to pool/main/w/writer2latex/libwriter2latex-java-doc_0.5.0.2-1_all.deb libwriter2latex-java_0.5.0.2-1_all.deb to pool/main/w/writer2latex/libwriter2latex-java_0.5.0.2-1_all.deb openoffice.org-writer2latex_0.5.0.2-1_all.deb to pool/main/w/w

Processing of writer2latex_0.5.0.2-1_amd64.changes

writer2latex_0.5.0.2-1_amd64.changes uploaded successfully to localhost along with the files: writer2latex_0.5.0.2-1.dsc writer2latex_0.5.0.2.orig.tar.gz writer2latex_0.5.0.2-1.diff.gz writer2latex_0.5.0.2-1_all.deb writer2latex-manual_0.5.0.2-1_all.deb libwriter2latex-java-doc_0.5.0.2-

openoffice.org-testautomation_3.0.0~rc2-1_powerpc.changes is NEW

openoffice.org-qa-ui-tests_3.0.0~rc2-1_all.deb to pool/main/o/openoffice.org-testautomation/openoffice.org-qa-ui-tests_3.0.0~rc2-1_all.deb (new) openoffice.org-testautomation_3.0.0~rc2-1.diff.gz extra devel (new) openoffice.org-testautomation_3.0.0~rc2-1.dsc extra devel (new) openoffice.org-test

Processing of openoffice.org-testautomation_3.0.0~rc2-1_powerpc.changes

openoffice.org-testautomation_3.0.0~rc2-1_powerpc.changes uploaded successfully to localhost along with the files: openoffice.org-testautomation_3.0.0~rc2-1.dsc openoffice.org-testautomation_3.0.0~rc2.orig.tar.gz openoffice.org-testautomation_3.0.0~rc2-1.diff.gz openoffice.org-qa-ui-tests_

Bug#501000: openoffice.org: Incorrect import of text-entry fields on microsoft word .doc import

Hi, David Baron wrote: > > And: Did you try with the 3.0 rc packages? > If I install these (off Debian experimental), the 2.4.* from unstable will be > replaced. I can certainly try that but want to know that the 3.0rc will be > usable since I do need it for work. Should be (except when you use

Bug#501000: openoffice.org: Incorrect import of text-entry fields on microsoft word .doc import

On Sunday 05 October 2008 21:43:46 Rene Engelhard wrote: > Hi, > > David Baron wrote: > > Text-input fields on .doc files are incorrectly imported: > > Most get imported with their default/initial text rather than what had > > been entered to the fields One-character fields get imported as the > >

Bug#501000: openoffice.org: Incorrect import of text-entry fields on microsoft word .doc import

Hi, David Baron wrote: > Text-input fields on .doc files are incorrectly imported: > Most get imported with their default/initial text rather than what had been > entered to the fields > One-character fields get imported as the default character and is no longer a > field. > > This make interop

./packages/openofficeorg/3.0/experimental r1271: create symlink .config -> .dll.config

revno: 1271 committer: Rene Engelhard <[EMAIL PROTECTED]> branch nick: debian timestamp: Sun 2008-10-05 21:00:15 +0200 message: create symlink .config -> .dll.config modified: changelog rules === modified file 'changelog' --- a/chan

Bug#501028: marked as forwarded (python-uno: Can't get types when using Python bindings)

Your message dated Sun, 5 Oct 2008 20:39:31 +0200 with message-id <[EMAIL PROTECTED]> has caused the report #501028, regarding python-uno: Can't get types when using Python bindings to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED] (NB: If you are a syst

Bug#501028: python-uno: Can't get types when using Python bindings

tag 501028 + confirmed # I fear it's grave, it breaks python-uno usage in most cases, doesn't it? severity 501028 grave thanks Hi, Daniel Watkins wrote: > >>> import uno > >>> uno.getClass('com.sun.star.awt.WindowDescriptor') > Traceback (most recent call last): > File "", line 1, in > File

Processed: Re: Bug#501028: python-uno: Can't get types when using Python bindings

Processing commands for [EMAIL PROTECTED]: > tag 501028 + confirmed Bug#501028: python-uno: Can't get types when using Python bindings There were no tags set. Tags added: confirmed > # I fear it's grave, it breaks python-uno usage in most cases, doesn't it? > severity 501028 grave Bug#501028: pyt