Am 06/06/2014 08:54 AM, schrieb Andrea Pescetti:
Marcus (OOo) wrote:
sure both buttons should react independent of each other. I've fixed
this.
Regarding the styling, this is indeed really a question of taste. To see
the difference maybe better, I've styled both buttons different.
I like the
On 30/05/2014 Marcus (OOo) wrote:
The both download buttons have now a hover over effect. They are
displayed inverted.
So, what do think is better as permanent design?
- Go back as it was before:
Light background, dark border, dark text
This is highly subjective, but this version looks
Am 06/05/2014 01:03 PM, schrieb Andrea Pescetti:
On 30/05/2014 Marcus (OOo) wrote:
The both download buttons have now a hover over effect. They are
displayed inverted.
So, what do think is better as permanent design?
- Go back as it was before:
Light background, dark border, dark text
This is
On 06/05/2014 03:38 PM, Marcus (OOo) wrote:
Am 06/05/2014 01:03 PM, schrieb Andrea Pescetti:
On 30/05/2014 Marcus (OOo) wrote:
The both download buttons have now a hover over effect. They are
displayed inverted.
So, what do think is better as permanent design?
- Go back as it was before:
Am 06/06/2014 01:10 AM, schrieb Kay Schenk:
On 06/05/2014 03:38 PM, Marcus (OOo) wrote:
Am 06/05/2014 01:03 PM, schrieb Andrea Pescetti:
On 30/05/2014 Marcus (OOo) wrote:
The both download buttons have now a hover over effect. They are
displayed inverted.
So, what do think is better as
.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not
working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the right
hand
:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not
working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the
right
hand nav bar - delete duplicates
how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not
working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the right
hand nav bar - delete duplicates, change order/positions, delete if
not needed here, etc
install + langpack.
- When choices are done a little help icon is shown. Click on it to get
to a help text for full install vs. langpack.
- Some release data is shown like in the green box.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work
Am 05/05/2014 01:29 AM, schrieb sebb:
On 4 May 2014 17:37, Marcus (OOo)marcus.m...@wtnet.de wrote:
As an aside, the information page about language packs could perhaps
describe how dictionaries compare with language packs. Do language
packs include any dictionaries? Or do they just include
On Sat, May 31, 2014 at 4:43 AM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Am 05/05/2014 01:29 AM, schrieb sebb:
On 4 May 2014 17:37, Marcus (OOo)marcus.m...@wtnet.de wrote:
As an aside, the information page about language packs could perhaps
describe how dictionaries compare with language
working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not
working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the
right
hand nav bar - delete
but it shows
already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not
working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the
right
hand nav bar - delete duplicates, change order/positions, delete if
not needed here
for selected full install + langpack.
- When choices are done a little help icon is shown. Click on it
to get
to a help text for full install vs. langpack.
- Some release data is shown like in the green box.
What is not yet working:
- The version dropdown box has no effect yet but it shows
already how
. langpack.
- Some release data is shown like in the green box.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not working.
What are the next steps:
- Reduce
already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not
working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the right
hand nav bar - delete duplicates, change order/positions, delete if
not needed here
:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not
working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the right
hand nav bar - delete duplicates
on it
to get
to a help text for full install vs. langpack.
- Some release data is shown like in the green box.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something
On 26/05/2014 Marcus (OOo) wrote:
Am 05/26/2014 10:34 PM, schrieb Andrea Pescetti:
I read his mail in this discussion as when you publish, you always
publish the whole thing ...
Sorry, I still can edit, update and publish a single file.
What's the problem to try again on your side?
OK, so I
Am 05/27/2014 10:15 PM, schrieb Andrea Pescetti:
On 26/05/2014 Marcus (OOo) wrote:
Am 05/26/2014 10:34 PM, schrieb Andrea Pescetti:
I read his mail in this discussion as when you publish, you always
publish the whole thing ...
Sorry, I still can edit, update and publish a single file.
What's
@Joe:
See my last my mail.
Lesson learned:
I've just seen what was updated in my workspace. But there is no hint
that other commits will be taken into account, too. Until you open this
link:
https://cms.apache.org/ooo-site/publish?diff=1
As here the truth is shown.
So finally, believe in
On 05/27/2014 01:30 PM, Marcus (OOo) wrote:
@Joe:
See my last my mail.
Lesson learned:
I've just seen what was updated in my workspace. But there is no hint
that other commits will be taken into account, too. Until you open this
link:
https://cms.apache.org/ooo-site/publish?diff=1
As
-green,
no links besides the both little icons,
doesn't change when different items were chosen
And I've no clue for now how it looks like on Firefox and Safari on
OS X.
mmh, the drop down boxes have still different height and look not so
good on Firefox
http://people.apache.org/~jsc/test
On Fri, May 23, 2014 at 11:23 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Marcus (OOo) wrote:
[...] http://ooo-site.staging.apache.org/download/test/
index_droplist.html
[...]
Unfortunately, there was no IE available. Can someone of you test this
please?
Win, IE10 – looks fine;
Win,
Am 05/26/2014 04:34 PM, schrieb Tal Daniel:
On Fri, May 23, 2014 at 11:23 PM, Marcus (OOo)marcus.m...@wtnet.de wrote:
Marcus (OOo) wrote:
[...] http://ooo-site.staging.apache.org/download/test/
index_droplist.html
[...]
Unfortunately, there was no IE available. Can someone of you test
but they work OK,
incomplete text in sub-green,
no links besides the both little icons,
doesn't change when different items were chosen
And I've no clue for now how it looks like on Firefox and Safari on
OS X.
mmh, the drop down boxes have still different height and look not so
good on Firefox
Am 05/19/2014 09:17 PM, schrieb Marcus (OOo):
Am 05/19/2014 09:51 AM, schrieb Andrea Pescetti:
On 29/04/2014 Marcus (OOo) wrote:
The main point is *where you are* in the CMS Browse View when you click
on the Update link.
I tried several times, but I'm not sure it works for me. Maybe it works
Marcus (OOo) wrote:
But when a single file, e.g., devbuild.html is shown and you click on
the Update link then only this file is updated and nothing else.
Please can you try it and confirm?
had you already a chance to retry?
I believe Joe made it clear that this won't work either. To be
Am 05/26/2014 10:34 PM, schrieb Andrea Pescetti:
Marcus (OOo) wrote:
But when a single file, e.g., devbuild.html is shown and you click on
the Update link then only this file is updated and nothing else.
Please can you try it and confirm?
had you already a chance to retry?
I believe Joe made
,
doesn't change when different items were chosen
And I've no clue for now how it looks like on Firefox and Safari on
OS X.
mmh, the drop down boxes have still different height and look not so
good on Firefox
http://people.apache.org/~jsc/test/Firefox_downloadbox.png
That's strange as with Firefox
,
doesn't change when different items were chosen
And I've no clue for now how it looks like on Firefox and Safari on OS X.
mmh, the drop down boxes have still different height and look not so
good on Firefox
http://people.apache.org/~jsc/test/Firefox_downloadbox.png
And Safari
Hi,
On 19.05.2014 23:56, Joe Schaefer wrote:
I think there's some confusion about what is actually happening
when you click on the Update link in the webgui. All that does
is run
% svn up /path/to/underlying/svn/resource
on the CMS server. When you publish you are essentially doing
% svn
,
no links besides the both little icons,
doesn't change when different items were chosen
And I've no clue for now how it looks like on Firefox and Safari on OS X.
mmh, the drop down boxes have still different height and look not so
good on Firefox
http://people.apache.org/~jsc
were chosen
And I've no clue for now how it looks like on Firefox and Safari on OS X.
Try www.browsershots.org?
Sure but I have made the experience that not all combinations are
available (e.g., Mac browsers are completely missing) or the request
expiring very fast.
However, a few minutes I
.
- When choices are done a little help icon is shown. Click on it to get
to a help text for full install vs. langpack.
- Some release data is shown like in the green box.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely
Marcus (OOo) wrote:
This weekend just a little update as I was not able to do more work
(healthy problem):
http://ooo-site.staging.apache.org/download/test/index_droplist.html
It's nice! I would say it's almost done. It works correctly for me.
Maybe, to simplify it further, I would remove the
On 29/04/2014 Marcus (OOo) wrote:
The main point is *where you are* in the CMS Browse View when you click
on the Update link.
I tried several times, but I'm not sure it works for me. Maybe it works
if we see update as update this directory.
Example to update and publish only a file:
1. In
chosen
And I've no clue for now how it looks like on Firefox and Safari on OS X.
So, sorry, but I fear there is some more work needed.
Maybe, to simplify it further, I would remove the 32-bit from Windows
since we are not offering anything else for Windows; so users won't be
confused.
Done
Am 05/19/2014 09:51 AM, schrieb Andrea Pescetti:
On 29/04/2014 Marcus (OOo) wrote:
The main point is *where you are* in the CMS Browse View when you click
on the Update link.
I tried several times, but I'm not sure it works for me. Maybe it works
if we see update as update this directory.
PM, schrieb Jürgen Schmidt:
Keep in mind that when you publish a page all pending changes will be
published as well. It is no local update of your changes only. Just as
reminder, it's a not so nice side effect of the CMS
It seems this wonderful feature is unknown. So let me explain how
Sorry but technically the CMS publishes all committed
changes to the staging site. The only way to partition
changes is to partition your commits.
On Monday, May 19, 2014 3:17 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Am 05/19/2014 09:51 AM, schrieb Andrea Pescetti:
On 29/04/2014
Am 05/19/2014 09:20 PM, schrieb Joe Schaefer:
Sorry but technically the CMS publishes all committed
changes to the staging site. The only way to partition
changes is to partition your commits.
but which data will be published: the content of the SVN repository or
the content of the personal
I think there's some confusion about what is actually happening
when you click on the Update link in the webgui. All that does
is run
% svn up /path/to/underlying/svn/resource
on the CMS server. When you publish you are essentially doing
% svn rm
like in the green box.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not working.
What are the next steps:
- Reduce the additional links in the green box and re
. It is no local update of your changes only. Just as
reminder, it's a not so nice side effect of the CMS
It seems this wonderful feature is unknown. So let me explain how to
publish only your updates: :-)
The main point is *where you are* in the CMS Browse View when you click
on the Update link
that when you publish a page all pending changes will be
published as well. It is no local update of your changes only. Just as
reminder, it's a not so nice side effect of the CMS
It seems this wonderful feature is unknown. So let me explain how to
publish only your updates: :-)
The main
:
- Bye, bye grey color - hello green freshness.
I would recommend styling the select boxes, here is an example of how CSS
can style them:
http://bavotasan.com/2011/style-select-box-using-only-css/
The code should be something like the following:
div class=styled-select
select
...
/div
help *what* to write - text or button or both or
something else ...
So, thanks for your suggestion.
As an aside, the information page about language packs could perhaps
describe how dictionaries compare with language packs. Do language
packs include any dictionaries? Or do they just include
On 7 May 2014 00:10, Marcus (OOo) marcus.m...@wtnet.de wrote:
Am 05/06/2014 02:24 AM, schrieb sebb:
On 5 May 2014 20:00, Marcus (OOo)marcus.m...@wtnet.de wrote:
Am 05/05/2014 01:29 AM, schrieb sebb:
On 4 May 2014 17:37, Marcus (OOo)marcus.m...@wtnet.de wrote:
Another update, seems
would recommend styling the select boxes, here is an example of how CSS
can style them:
http://bavotasan.com/2011/style-select-box-using-only-css/
The code should be something like the following:
div class=styled-select
select
...
/div
and the css:
#lang #os, #ver {
background
help *what* to write - text or button or both
or something else ...
So, thanks for your suggestion.
As an aside, the information page about language packs could perhaps
describe how dictionaries compare with language packs. Do language
packs include any dictionaries? Or do they just include
, thanks for your suggestion.
As an aside, the information page about language packs could perhaps
describe how dictionaries compare with language packs. Do language
packs include any dictionaries? Or do they just include the text
strings used in the application?
I found the page quite
is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
Indeed, selecting Mac OS X 32-bit offers 4.1.0 too, but I think this
is under control.
Luckily it's the 64-bit file that is offered. ;-) But, yes, as soon as the
version selection
no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something is not working.
What are the next steps:
- Reduce the additional links in the green box and re-work in the right
hand nav bar - delete duplicates, change order/positions
) there rather than the question mark,
which seems to explain an error.
OK, I will change it.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
Indeed, selecting Mac OS X 32-bit offers 4.1.0 too, but I think this
is under control
about language packs could perhaps
describe how dictionaries compare with language packs. Do language
packs include any dictionaries? Or do they just include the text
strings used in the application?
I found the page quite difficult to follow.
What is not yet working:
- The version drop-down-box
with guessed values.
I like the idea of an icon for explanations, but I would use an
information sign (circled i) there rather than the question mark,
which seems to explain an error.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work
Am 05/03/2014 04:05 AM, schrieb sebb:
How about presetting the fields according to the autodetected values,
where possible?
actually I've planned this when the green and grey box will be combined
but ...
Then if the auto-detection works for some of the fields it will reduce
the work
an
information sign (circled i) there rather than the question mark,
which seems to explain an error.
OK, I will change it.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
Indeed, selecting Mac OS X 32-bit offers 4.1.0 too, but I
On 3 May 2014 10:30, Marcus (OOo) marcus.m...@wtnet.de wrote:
Am 05/03/2014 04:05 AM, schrieb sebb:
How about presetting the fields according to the autodetected values,
where possible?
actually I've planned this when the green and grey box will be combined but
...
Then if the auto
. Click on it to get
to a help text for full install vs. langpack.
- Some release data is shown like in the green box.
What is not yet working:
- The version dropdown box has no effect yet but it shows already how
it could work (likely).
- I've not tested with all browsers. So, maybe something
How about presetting the fields according to the autodetected values,
where possible?
Then if the auto-detection works for some of the fields it will reduce
the work for the user.
Also if the autodetection works, but the user wants to download for a
differnt OS or language it also reduces
Hello,
I just adjusted the German Home page, so far only in the staging area:
http://ooo-site.staging.apache.org/de/index.html
in which file I can, in the CMS, the line / link:
Apache OpenOffice 4.0.1 is available!
adapt to the above page?
Greetings,
Jörg
On Tue, Apr 29, 2014 at 8:12 AM, Jörg Schmidt joe...@j-m-schmidt.de wrote:
Hello,
I just adjusted the German Home page, so far only in the staging area:
http://ooo-site.staging.apache.org/de/index.html
in which file I can, in the CMS, the line / link:
Apache OpenOffice 4.0.1 is available!
.
Thank you.
the updated de-page is now online:
http://www.openoffice.org/de/
Please a detail:
I have the blog linked by:
https://blogs.apache.org/OOo/date/20140429
that will work, but is not quite right.
How do I find the correct link to the post:
The Apache OpenOffice project announce
and announce URL fields.
Thank you.
the updated de-page is now online:
http://www.openoffice.org/de/
Please a detail:
I have the blog linked by:
https://blogs.apache.org/OOo/date/20140429
that will work, but is not quite right.
How do I find the correct link to the post
on Tuesday, April 29, 2014 3:45 PM Jürgen Schmidt wrote:
browse the blog entry and copy the link
https://blogs.apache.org/OOo/entry/the_apache_openoffice_proje
ct_announce
mmh ... it is generally true that the part
the_apache_openoffice_project_announce corresponds to what is specified in
Jörg Schmidt wrote:
on Tuesday, April 29, 2014 3:45 PM Jürgen Schmidt wrote:
browse the blog entry and copy the link
mmh ... it is generally true that the part
the_apache_openoffice_project_announce corresponds to what is specified in
the source code of the page as id?
OK, so let me
explain how to
publish only your updates: :-)
The main point is *where you are* in the CMS Browse View when you click
on the Update link.
Example to update and publish only a file:
1. In your browser open, e.g.,
www.openoffice.org/my-dir/my-subdir/index.html.
2. Open the CMS via
On 4/28/14 12:29 AM, Kay Schenk wrote:
On Sun, Apr 27, 2014 at 11:19 AM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the green box is fast and easy
- Downloading a
Hi,
On 28.04.2014 10:38, Jürgen Schmidt wrote:
On 4/28/14 12:29 AM, Kay Schenk wrote:
On Sun, Apr 27, 2014 at 11:19 AM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the
On Sun, Apr 27, Marcus wrote:
[...] I made some progress about a long-term problem:
- Downloading the offered file via the green box is fast and easy
- Downloading a different file than the offered is not
[...] Therefore I've thought of making another offer directly on the main
download
On Sun, Apr 27, 2014 at 2:19 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the green box is fast and easy
- Downloading a different file than the offered is not
Via the
On Mon, 28 Apr 2014 12:19:20 -0400
Rob Weir robw...@apache.org wrote:
On Sun, Apr 27, 2014 at 2:19 PM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the green box is
guess of what the user wants?
-Rob
Thanks in advance.
Marcus
The grey box should have an explicit reference to the version number (4.0.1 in
this case)
Right, for the moment I've added this into the headline.
Lets see how this can be kept after some redesigns.
Marcus
Am 04/28/2014 06:19 PM, schrieb Rob Weir:
On Sun, Apr 27, 2014 at 2:19 PM, Marcus (OOo)marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the green box is fast and easy
- Downloading a
Am 04/28/2014 12:29 AM, schrieb Kay Schenk:
On Sun, Apr 27, 2014 at 11:19 AM, Marcus (OOo)marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the green box is fast and easy
- Downloading a
Am 04/28/2014 10:38 AM, schrieb Jürgen Schmidt:
On 4/28/14 12:29 AM, Kay Schenk wrote:
On Sun, Apr 27, 2014 at 11:19 AM, Marcus (OOo)marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the
for other version, language, or OS.
This link was not often seen in the past - at least we got several
questions how to get other builds. So, to be honest, I would doubt that
the grey box would be then seen by all users. ;-)
Great work :)
Thanks
Marcus
On Mon, Apr 28, Marcus wrote:
Am 04/28/2014 06:00 PM, schrieb Tal Daniel:
[...]Looks nice and more compact, Marcus. [...] I'd like to suggest to
drop the [redundant] line Click here to download for: in the green box,
and the
line Choose an OS, then the language in the gray box, which you
Am 04/28/2014 10:30 PM, schrieb Tal Daniel:
On Mon, Apr 28, Marcus wrote:
Am 04/28/2014 06:00 PM, schrieb Tal Daniel:
[...]Looks nice and more compact, Marcus. [...] I'd like to suggest to
drop the [redundant] line Click here to download for: in the green box,
and the
line Choose an OS,
Thanks a lot for your input.
A few of them (delete some obviously not needed text, make the choice
order of the drop-dwn boxes irrelevant) are already committed. But the
most need more time.
Please don't expect to have this full-featured for the AOO 4.1.0
release. I need more time to do all
On Sun, Apr 27, 2014 at 11:19 AM, Marcus (OOo) marcus.m...@wtnet.de wrote:
Hi all,
while enjoying the Easter time I made some progress about a long-term
problem:
- Downloading the offered file via the green box is fast and easy
- Downloading a different file than the offered is not
Via
Veronica Sawyer
as to how to proceed.
--
Regards,
Surya
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Am 03/27/2014 07:58 AM, schrieb Herbert Duerr:
On 03/26/2014 11:00 PM, Andrea Pescetti wrote:
Marcus (OOo) wrote:
In the last weeks I've seen different styles of how to write an issue
number in the commit messages:
#i123456#
#123456#
i123456
123456
Does it still matter how it is written
Date: Wed, 26 Mar 2014 20:34:16 +0100
From: marcus.m...@wtnet.de
To: dev@openoffice.apache.org
CC: oyvindp...@hotmail.com
Subject: Re: How to download your program?
Am 03/26/2014 03:32 AM, schrieb øyvind sørensen:
I tried again and it is still the same, i use google chrome browserI have also
That was a quick read.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
/download/test/analyze.html
Thanks in advance for your help.
Marcus
Date: Tue, 25 Mar 2014 23:40:21 +0100
From: marcus.m...@wtnet.de
To: dev@openoffice.apache.org
CC: oyvindp...@hotmail.com
Subject: Re: How to download your program?
Thanks for the data.
I think I've found the problem
In the last weeks I've seen different styles of how to write an issue
number in the commit messages:
#i123456#
#123456#
i123456
123456
Does it still matter how it is written? Or is it always recognized
correctly?
I know Herbert (hdu) has built a nice script to collect all fixes, to
see
Marcus (OOo) wrote:
In the last weeks I've seen different styles of how to write an issue
number in the commit messages:
#i123456#
#123456#
i123456
123456
Does it still matter how it is written? Or is it always recognized
correctly?
The first two options do both work and it is a matter
Apache OpenOffice 4.0.1Click here to download for:
Windows (EXE) and English (US) | ~137 MByte | Released: 2013-Oct-01
Signatures and hashes: KEYS , ASC , MD5 , SHA256 , How to verify? | Release
Notes |
Get all platforms, languages, language packs | Source code and SDK |
Portable USB versions
Danette Fernando
antivirus, who
said it was clean.
I didnt notice anything unusal yet so i think it was good.
I tro, håp og kjærlighet Øyvind Sørensen
Date: Mon, 24 Mar 2014 20:57:32 +0100
From: marcus.m...@wtnet.de
To: dev@openoffice.apache.org
CC: oyvindp...@hotmail.com
Subject: Re: How to download your
Øyvind Sørensen
Date: Tue, 25 Mar 2014 23:40:21 +0100
From: marcus.m...@wtnet.de
To: dev@openoffice.apache.org
CC: oyvindp...@hotmail.com
Subject: Re: How to download your program?
Thanks for the data.
I think I've found the problem and have done a fix. With my testing it
works
dismissing CNET and other ways to get your
software i finally got a downloadable solution. I do not know what i did or how
i got there, but i can say that I am now happy with your software and have got
the documents i needed written and PDF-ified
I write this so that other can enjoy the benefit
easily
obtainable, but i had problems utilizing their program.Then i did more
(several) google search for openoffice download, and after dismissing CNET
and other ways to get your software i finally got a downloadable solution. I
do not know what i did or how i got there, but i can say that I
did or how i got there, but i can say that I am now happy
with your software and have got the documents i needed written and PDF-ified
I write this so that other can enjoy the benefit of using your very great
software.Please make a link to download Apache openoffice.exe on yor
website.
I tro
) google search for
openoffice download, and after dismissing CNET and other ways to get your
software i finally got a downloadable solution. I do not know what i did or how
i got there, but i can say that I am now happy with your software and have got
the documents i needed written and PDF-ified
I
mailto:dev@openoffice.apache.org?subject=Completed%20How%20the%20Apache%20OpenOffice%20Project%20Works
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:
301 - 400 of 631 matches
Mail list logo
