Re: Printing Envelopes, Sent, Friday. 2-9-18.

[Peter Kovacs]

Hi OpenOffice User List,


I pass this request to you.

If there are problems that we have to solve by coding,

please send us a note to the dev list or open a bug.


Thanks for your continous effort to help users!


All the Best

Peter


On 09.02.2018 16:29, Ddardanell wrote:

Hi, I just bought a new Brother All in one Printer.

Model # (L8900cdw), and it works
Fine but I can't find out how to

Print Envelopes?. Now, when I
Had my Epson ink jet printer

There was no problem, but I can't
Seem to find the Option now

With the new printer too print
Envelopes?.

And I believe I have version 4.1.5.
Can you take me by the hand, and

Help me figure out what I am doing
Wrong?.

Thanks so much, and I look forward too your response.

Sincerely,
Don G Dardanelli
1168 Pembridge Dr.
San Jose, California. 95118

PH: (408-202-4624)
E-Mail: (ddardan...@aol.com).

Sent from my Sony Xperia™ smartphone



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Windows developent plan

[Peter Kovacs]

+1 sounds fair.


On 09.02.2018 22:48, Marcus wrote:

Am 09.02.2018 um 22:44 schrieb Peter Kovacs:

It was only an idea. No special build we just keep the target.

How about update to the MSVC2017?


we simple have to try which version is the most recent to get the 
fewest problems. When it fits then we can use it. ;-)


Marcus




On 09.02.2018 22:07, Marcus wrote:

Am 09.02.2018 um 06:13 schrieb Keith N. McKenna:

On 2/8/2018 6:25 PM, Marcus wrote:

Am 08.02.2018 um 21:14 schrieb Peter Kovacs:

According to ReactOS team MSVC 2010 still supports WinXP target.
I say we should keep the WinXP support up as long as the ReactOS 
team

does not support WinNT5 binaries.


OK, when we can combine 1) a compatible and still supported MSVC 
and 2)
it's still possible to use OpenOffice with WinXP, then sure let's 
do it.



It is a good and sound strategy, we would promote another OpenSource
Project.

I think build additional legacy WinXP binary will not hurt us, 
and it


Ahm, I hope this is a typo. I don't want to have separate binaries 
just

for WinXP and all newer Windows versions. ;-)


If we are to upgrade to Java 9 for windows by default wouldn't we have
to make separate builds for all 32 bit versions of Windows as 
Oracle did

not release a 32 bit version of Java 9?


maybe, but it's about WinXP. Here we shouldn't create a special build.

Marcus




might be not so much more work. We could explain this if we are
releasing 4.2.0 before ReactOS has made the transition.
That would fit to our strategy in Total. We also do support AmigaOS
and OS/2 warp inofficially. Maybe it would bring us sympathy from 
another


Inofficially means concrete: We can bring in fixes into SVN, so that
others are able to build on other platforms like OS/2. But that is 
all

as building and distribution is happening outside of the ASF.


Community if we promote their target.
Do you agree on the strategy or do you think it would cost us to 
much

workload?


Like I wrote above, let's do it if we can have it for a cheap 
"price".



I have found 2 more Windows action Items I forgot about:

a) MSI installer


We have already a MSI installation. What exactly do you have in mind?


b) signed install binary.

Do you think these Items should be trackked too?
If so where should they be on our list?


Even when signing is complicated as at the moment we need to start at
zero (analysis and development) it's the top priority as it would 
show a

much better integration into modern Windows releases.

My 2 ct.

Marcus




On 08.02.2018 07:35, Mechtilde wrote:

Hello,

I would guess it.

If someone still have a Win-XP system can test if it also works 
on Win

XP. But Win XP is end of live for a long time.

User can use 4.1.5 as long as they use Win XP.

Kind regards


Am 08.02.2018 um 00:58 schrieb Pedro Lino:



Thats the points I am aware of. Are there more Windows specific
points?

Does upgrade from MSVC2008 mean dropping support for Win XP? The
recently released LO 6.0 32bit requires at least Windows 7...



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [proposal] going Agile

[Peter Kovacs]

On 09.02.2018 23:08, Marcus wrote:

Am 08.02.2018 um 00:32 schrieb Andrea Pescetti:

Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as 
much as we can.

it depends what you mean with agile.

IMHO forget Scrum as we are not the community to get a commitment for 
this.

Why? What does our community do not like about scrum?
We do not like the Values of scrum?
Focus
Openess
Respect
Commitment
Courage

Or maybe we do not like the pillars?
Transparency, Inspect and adapt?
;)

Agreed, I think we can not use SCRUM in the same way Companies do, too. 
But I think we can use the Idea of scrum to work together and to 
simplify our work. What would you use to make our work simple?
Why do you think Ordering our Bugs in a List and add details to them 
will not bring us forward?


Kanban would be nice.

YAY!
I take this as a success!! :-D
One step forward. Thousands more to go.
So where you would establish the board? - Use trello? Confluence? 
(No ;) )
Jira has a Backlog and a Kanban board integrated which I am told are 
very easy to use (Drag & drop I hope...)


At the end it's a bit problematic for us with the attributes of 
volunteers, their unpredictable working time (time to work on 
OpenOffice tasks) and the number of volunteers.


However, we should try to keep it simple as Product Backlop, Product 
Owner, Tasks, Sub-Tasks, Jira, Confluence etc. would be much too much 
complexity for us when doing/using all of them.
Maybe I have learned a total different scrum then you did? - Agile does 
not mean to use everything like a fixed ruleset. To me SCRUM is a 
template to start with It just tells us what prooved to be working well. 
But How and what we can use from the framework, is up to us.


Again. Only Product Backlog, Product Owner, and a Kanban board are on 
the table as to be used. And I do only want the Product owner so we have 
some steward for the list. I am totaly fine with a Release Manager 
looking into it.
I have not explained to maximize Value and Output, since I do not 
believe we do need to maximize Value and Output, since we are Open 
Source Volunteering Community and not OpenSource Commercial Product. 
Small but important difference not to forget. (If we get OpenSource 
Comercial part, we have to make sure they can spend their energy on 
maximizing Value. ;) )


You agree?

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [proposal] going Agile

[Peter Kovacs]

Migration would be done by infra. They wrote up everything need to know:

https://wiki.apache.org/general/ApacheBugzillaToJiraMigration


Again, it is not about the tool it is about the workflow. I would like 
to have a Kanbanboard, to get transparency what is worked on, who can I 
approach if I have a volunteer to work together. New Volunteers need 
someone they can follow.


I want to have a Backlog to define what is important to do next, and to 
fill the detailed steps together what we need to do. Maybe we could 
together fill out so much detail, that it is easy for everyone to start 
on the topic.



That is the original proposal. I know that Jira is _the_ industry tool 
to this. Every major professional major Project uses Jira. It would not 
be so popular if it would not have a certain quality.


I know that you complained onec there are so many differnt links to note 
and tools that we have in our arsenal.


Jira could be reduce the lot. Thats why I think it is convenient.


BTW. If we start using Kanban, I will reach out to the one Volunteer who 
volunteered and loves Kanban if want to have a try with us, we are now 
following his way (more or less...) Maybe he jumps at it.


We had another Volunteer who said: tell me what to do I do it. But I do 
not have the interest to figure it out on my own. We can currently not 
use these people. With Backlog and Board we can.


That would mean 2 more developers. Propably. Maybe they quick because it 
is frustrating to build OpenOffice. *ROFL*




On 09.02.2018 23:05, Marcus wrote:
I would prefer to avoid the upheaval of switching to a different 
issue tracker if at all possible.


+1

Jira is just another tool that wouldn't bring us any nearer to closed 
issues. BTW, start new? Then you would trash all old issues which 
isn't a good thing. Move them over to Jira? Great, who is the 
volunteer to do the migration? ;-)


But Confluence can bring us some overview. We can structure similar BZ 
issues to packages and then we can work on them. 

Re: [proposal] going Agile

[Marcus]

Am 08.02.2018 um 00:32 schrieb Andrea Pescetti:

Peter Kovacs wrote:
I would like to propose that we apply Agile development methods as 
much as we can.


it depends what you mean with agile.

IMHO forget Scrum as we are not the community to get a commitment for this.

Kanban would be nice.

At the end it's a bit problematic for us with the attributes of 
volunteers, their unpredictable working time (time to work on OpenOffice 
tasks) and the number of volunteers.


However, we should try to keep it simple as Product Backlop, Product 
Owner, Tasks, Sub-Tasks, Jira, Confluence etc. would be much too much 
complexity for us when doing/using all of them.


My 2 ct.
(also with my years of experience as Scrum Product Owner)

Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [proposal] going Agile

[Marcus]

Am 09.02.2018 um 01:19 schrieb Patricia Shanahan:

On February 8, 2018, at 5:51 AM, Peter Kovacs  wrote:


# Start spreading knowledge in our development team.



1) I would like to propose a Product Backlog / OIL (OpenIssue) List
to priorize Issues we need to work on. The most Valueable item comes
to the top, the least to the bottom. What Value exactly is is up to
discussion.


Theoretically, we have a list of issues in Bugzilla with target 4.2.0.
Validating them all and/or setting targets will basically give you
what you wish. I think Bugzilla has some concept of an issue weight
that would more or less allow to prioritize issues with the current
tooling, so this can be done. At least, once we agree on list on a
series of "must-haves" for 4.2.0, these could be turned into something
similar to your backlog.

Maybe we should not discuss tooling now. I think in the end it has to
work. Jira is mostly a convenient choice. But we can think of all other
sort of combinations. (However we have already a lot of Tools.So I would
rather try to reduce those. We can try Bugzilla, but i do not want to
start modifying Bugzilla in order to get what we need.


I would prefer to avoid the upheaval of switching to a different issue tracker 
if at all possible.


+1

Jira is just another tool that wouldn't bring us any nearer to closed 
issues. BTW, start new? Then you would trash all old issues which isn't 
a good thing. Move them over to Jira? Great, who is the volunteer to do 
the migration? ;-)


But Confluence can bring us some overview. We can structure similar BZ 
issues to packages and then we can work on them.


Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Windows developent plan

[Marcus]

Am 09.02.2018 um 22:44 schrieb Peter Kovacs:

It was only an idea. No special build we just keep the target.

How about update to the MSVC2017?


we simple have to try which version is the most recent to get the fewest 
problems. When it fits then we can use it. ;-)


Marcus




On 09.02.2018 22:07, Marcus wrote:

Am 09.02.2018 um 06:13 schrieb Keith N. McKenna:

On 2/8/2018 6:25 PM, Marcus wrote:

Am 08.02.2018 um 21:14 schrieb Peter Kovacs:

According to ReactOS team MSVC 2010 still supports WinXP target.
I say we should keep the WinXP support up as long as the ReactOS team
does not support WinNT5 binaries.


OK, when we can combine 1) a compatible and still supported MSVC and 2)
it's still possible to use OpenOffice with WinXP, then sure let's do 
it.



It is a good and sound strategy, we would promote another OpenSource
Project.

I think build additional legacy WinXP binary will not hurt us, and it


Ahm, I hope this is a typo. I don't want to have separate binaries just
for WinXP and all newer Windows versions. ;-)


If we are to upgrade to Java 9 for windows by default wouldn't we have
to make separate builds for all 32 bit versions of Windows as Oracle did
not release a 32 bit version of Java 9?


maybe, but it's about WinXP. Here we shouldn't create a special build.

Marcus




might be not so much more work. We could explain this if we are
releasing 4.2.0 before ReactOS has made the transition.
That would fit to our strategy in Total. We also do support AmigaOS
and OS/2 warp inofficially. Maybe it would bring us sympathy from 
another


Inofficially means concrete: We can bring in fixes into SVN, so that
others are able to build on other platforms like OS/2. But that is all
as building and distribution is happening outside of the ASF.


Community if we promote their target.
Do you agree on the strategy or do you think it would cost us to much
workload?


Like I wrote above, let's do it if we can have it for a cheap "price".


I have found 2 more Windows action Items I forgot about:

a) MSI installer


We have already a MSI installation. What exactly do you have in mind?


b) signed install binary.

Do you think these Items should be trackked too?
If so where should they be on our list?


Even when signing is complicated as at the moment we need to start at
zero (analysis and development) it's the top priority as it would 
show a

much better integration into modern Windows releases.

My 2 ct.

Marcus




On 08.02.2018 07:35, Mechtilde wrote:

Hello,

I would guess it.

If someone still have a Win-XP system can test if it also works on 
Win

XP. But Win XP is end of live for a long time.

User can use 4.1.5 as long as they use Win XP.

Kind regards


Am 08.02.2018 um 00:58 schrieb Pedro Lino:



Thats the points I am aware of. Are there more Windows specific
points?

Does upgrade from MSVC2008 mean dropping support for Win XP? The
recently released LO 6.0 32bit requires at least Windows 7...



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Windows developent plan

[Peter Kovacs]

It was only an idea. No special build we just keep the target.

How about update to the MSVC2017?


On 09.02.2018 22:07, Marcus wrote:

Am 09.02.2018 um 06:13 schrieb Keith N. McKenna:

On 2/8/2018 6:25 PM, Marcus wrote:

Am 08.02.2018 um 21:14 schrieb Peter Kovacs:

According to ReactOS team MSVC 2010 still supports WinXP target.
I say we should keep the WinXP support up as long as the ReactOS team
does not support WinNT5 binaries.


OK, when we can combine 1) a compatible and still supported MSVC and 2)
it's still possible to use OpenOffice with WinXP, then sure let's do 
it.



It is a good and sound strategy, we would promote another OpenSource
Project.

I think build additional legacy WinXP binary will not hurt us, and it


Ahm, I hope this is a typo. I don't want to have separate binaries just
for WinXP and all newer Windows versions. ;-)


If we are to upgrade to Java 9 for windows by default wouldn't we have
to make separate builds for all 32 bit versions of Windows as Oracle did
not release a 32 bit version of Java 9?


maybe, but it's about WinXP. Here we shouldn't create a special build.

Marcus




might be not so much more work. We could explain this if we are
releasing 4.2.0 before ReactOS has made the transition.
That would fit to our strategy in Total. We also do support AmigaOS
and OS/2 warp inofficially. Maybe it would bring us sympathy from 
another


Inofficially means concrete: We can bring in fixes into SVN, so that
others are able to build on other platforms like OS/2. But that is all
as building and distribution is happening outside of the ASF.


Community if we promote their target.
Do you agree on the strategy or do you think it would cost us to much
workload?


Like I wrote above, let's do it if we can have it for a cheap "price".


I have found 2 more Windows action Items I forgot about:

a) MSI installer


We have already a MSI installation. What exactly do you have in mind?


b) signed install binary.

Do you think these Items should be trackked too?
If so where should they be on our list?


Even when signing is complicated as at the moment we need to start at
zero (analysis and development) it's the top priority as it would 
show a

much better integration into modern Windows releases.

My 2 ct.

Marcus




On 08.02.2018 07:35, Mechtilde wrote:

Hello,

I would guess it.

If someone still have a Win-XP system can test if it also works on 
Win

XP. But Win XP is end of live for a long time.

User can use 4.1.5 as long as they use Win XP.

Kind regards


Am 08.02.2018 um 00:58 schrieb Pedro Lino:



Thats the points I am aware of. Are there more Windows specific
points?

Does upgrade from MSVC2008 mean dropping support for Win XP? The
recently released LO 6.0 32bit requires at least Windows 7...



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Windows developent plan

[Marcus]

Am 09.02.2018 um 06:13 schrieb Keith N. McKenna:

On 2/8/2018 6:25 PM, Marcus wrote:

Am 08.02.2018 um 21:14 schrieb Peter Kovacs:

According to ReactOS team MSVC 2010 still supports WinXP target.
I say we should keep the WinXP support up as long as the ReactOS team
does not support WinNT5 binaries.


OK, when we can combine 1) a compatible and still supported MSVC and 2)
it's still possible to use OpenOffice with WinXP, then sure let's do it.


It is a good and sound strategy, we would promote another OpenSource
Project.

I think build additional legacy WinXP binary will not hurt us, and it


Ahm, I hope this is a typo. I don't want to have separate binaries just
for WinXP and all newer Windows versions. ;-)


If we are to upgrade to Java 9 for windows by default wouldn't we have
to make separate builds for all 32 bit versions of Windows as Oracle did
not release a 32 bit version of Java 9?


maybe, but it's about WinXP. Here we shouldn't create a special build.

Marcus




might be not so much more work. We could explain this if we are
releasing 4.2.0 before ReactOS has made the transition.
That would fit to our strategy in Total. We also do support AmigaOS
and OS/2 warp inofficially. Maybe it would bring us sympathy from another


Inofficially means concrete: We can bring in fixes into SVN, so that
others are able to build on other platforms like OS/2. But that is all
as building and distribution is happening outside of the ASF.


Community if we promote their target.
Do you agree on the strategy or do you think it would cost us to much
workload?


Like I wrote above, let's do it if we can have it for a cheap "price".


I have found 2 more Windows action Items I forgot about:

a) MSI installer


We have already a MSI installation. What exactly do you have in mind?


b) signed install binary.

Do you think these Items should be trackked too?
If so where should they be on our list?


Even when signing is complicated as at the moment we need to start at
zero (analysis and development) it's the top priority as it would show a
much better integration into modern Windows releases.

My 2 ct.

Marcus




On 08.02.2018 07:35, Mechtilde wrote:

Hello,

I would guess it.

If someone still have a Win-XP system can test if it also works on Win
XP. But Win XP is end of live for a long time.

User can use 4.1.5 as long as they use Win XP.

Kind regards


Am 08.02.2018 um 00:58 schrieb Pedro Lino:



Thats the points I am aware of. Are there more Windows specific
points?

Does upgrade from MSVC2008 mean dropping support for Win XP? The
recently released LO 6.0 32bit requires at least Windows 7...



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [proposal] going Agile

[Peter Kovacs]

On 09.02.2018 01:19, Patricia Shanahan wrote:

On February 8, 2018, at 5:51 AM, Peter Kovacs  wrote:

# Devide the Project into different selfcontained parts. so we have
smaller chunks to swallow. (Maybe we should consider breaking the
compile Process into individual compile steps by package just to reduce
Complexity.)
How would this be different from what we have now? The code is already divided 
into modules, and the build process builds each to get the packages.
I wrote hasty. I do not know for sure since to me the build system is a 
big huge black box.

I want more transperency, better control over the code.
I think if we hard split the build and only build each package on their 
own we will gain a better view on the code. But I could be wrong.

At least I would like to have the option.

# Start spreading knowledge in our development team.
Maybe we should not discuss tooling now. I think in the end it has to
work. Jira is mostly a convenient choice. But we can think of all other
sort of combinations. (However we have already a lot of Tools.So I would
rather try to reduce those. We can try Bugzilla, but i do not want to
start modifying Bugzilla in order to get what we need.

I would prefer to avoid the upheaval of switching to a different issue tracker 
if at all possible.
The tool is not important. It is just a tool that has to serve a 
purpose. Important to me is that we change the method we work.

In my opinion, YAGNI is just as important for process design as for software 
design.
Thats the principle of lean management. In my opinion we currently work 
on this method, but keep the PMO structure that the the project was 
build on from the old days. And thats makeing it all difficult for everyone.

If we get to the point of having enough active volunteers that we need to think 
in terms of forming teams we will know a lot more about their skills, 
availability etc. and therefore be able to do a better job of organizing those 
teams.
We had 4 or 5 candidates. So far no one stayed. They had a look and went 
off. You can blame all sorts of things. In reality you have only control 
over one thing that is you. We do only have the power to change this 
project.

If we want that people stay, we need to change. Not other way round.

The question is how we want to change.
I like the family trait we have. I would like to use this trait to make 
people stay. Agile teams in my eyes will open a gate for new people into 
our community. They start learning some people from the community 
quickly and as they work they learn more. Becomming more attached. Thats 
why I am suggesting it.


What would you change with the ressources we have to make people stay?

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Printing Envelopes, Sent, Friday. 2-9-18.

[Ddardanell]

Hi, I just bought a new Brother All in one Printer. 

Model # (L8900cdw), and it works 
Fine but I can't find out how to 

Print Envelopes?. Now, when I 
Had my Epson ink jet printer 

There was no problem, but I can't 
Seem to find the Option now 

With the new printer too print
Envelopes?. 

And I believe I have version 4.1.5.
Can you take me by the hand, and 

Help me figure out what I am doing 
Wrong?. 

Thanks so much, and I look forward too your response. 

Sincerely, 
Don G Dardanelli 
1168 Pembridge Dr. 
San Jose, California. 95118 

PH: (408-202-4624) 
E-Mail: (ddardan...@aol.com). 

Sent from my Sony Xperia™ smartphone

Re: 4.2.0 minor errors

[Jim Jagielski]

Oh. Ugg. The hope was that these builds would address
that specific bug.

Just re-looked at the bug :/

> On Feb 9, 2018, at 8:00 AM, Rory O'Farrell  wrote:
> 
> On Fri, 9 Feb 2018 07:48:24 -0500
> Jim Jagielski > wrote:
> 
>> Can you try the versions from:
>> 
>>o http://people.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1823225/ 
>>  
>> > >
>> 
>> Thx!
> 
> I am actually using the 64 bit deb version 1823225
> 
> Rory
> 
> 
>> 
>>> On Feb 9, 2018, at 4:24 AM, Rory O'Farrell  wrote:
>>> 
>>> When I use 4.2.0, running on Xubuntu 16.04.03, to open an existing .odt 
>>> file I get a small popup that informs me of "general error".  The file then 
>>> opens correctly; starting 4.2.0 in a terminal gives no diagnostic.  Opening 
>>> Writer from the start centre there is no such error message; I can generate 
>>> a test document, but when I save, again I get an error "Error saving the 
>>> document Tom: General Error".  However the file Tom.odt is actually saved 
>>> (in spite of the error message), and will reopen giving the above "general 
>>> error" message,
>>> 
>>> Opening an existing simple spreadsheet - a short list of description and 
>>> amount - I get a Yellow exclamation mark and "Not all attributes could be 
>>> read"; on dismissing this, the sheet opens correctly.
>>> 
>>> 
>>> -- 
>>> Rory O'Farrell 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> 
> 
> 
> -- 
> Rory O'Farrell >
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> 
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
> 

Re: 4.2.0 minor errors

[Rory O'Farrell]

On Fri, 9 Feb 2018 07:48:24 -0500
Jim Jagielski  wrote:

> Can you try the versions from:
> 
> o http://people.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1823225/ 
> 
> 
> Thx!

I am actually using the 64 bit deb version 1823225

Rory


> 
> > On Feb 9, 2018, at 4:24 AM, Rory O'Farrell  wrote:
> > 
> > When I use 4.2.0, running on Xubuntu 16.04.03, to open an existing .odt 
> > file I get a small popup that informs me of "general error".  The file then 
> > opens correctly; starting 4.2.0 in a terminal gives no diagnostic.  Opening 
> > Writer from the start centre there is no such error message; I can generate 
> > a test document, but when I save, again I get an error "Error saving the 
> > document Tom: General Error".  However the file Tom.odt is actually saved 
> > (in spite of the error message), and will reopen giving the above "general 
> > error" message,
> > 
> > Opening an existing simple spreadsheet - a short list of description and 
> > amount - I get a Yellow exclamation mark and "Not all attributes could be 
> > read"; on dismissing this, the sheet opens correctly.
> > 
> > 
> > -- 
> > Rory O'Farrell 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > 
> 


-- 
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: 4.2.0 minor errors

[Jim Jagielski]

Can you try the versions from:

o http://people.apache.org/~jim/AOO-builds/AOO-4.2.0-dev-r1823225/ 


Thx!

> On Feb 9, 2018, at 4:24 AM, Rory O'Farrell  wrote:
> 
> When I use 4.2.0, running on Xubuntu 16.04.03, to open an existing .odt file 
> I get a small popup that informs me of "general error".  The file then opens 
> correctly; starting 4.2.0 in a terminal gives no diagnostic.  Opening Writer 
> from the start centre there is no such error message; I can generate a test 
> document, but when I save, again I get an error "Error saving the document 
> Tom: General Error".  However the file Tom.odt is actually saved (in spite of 
> the error message), and will reopen giving the above "general error" message,
> 
> Opening an existing simple spreadsheet - a short list of description and 
> amount - I get a Yellow exclamation mark and "Not all attributes could be 
> read"; on dismissing this, the sheet opens correctly.
> 
> 
> -- 
> Rory O'Farrell 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

Re: 4.2.0 minor errors

[Matthias Seidel]

See:
https://bz.apache.org/ooo/show_bug.cgi?id=127315

Regards, Matthias


Am 09.02.2018 um 10:24 schrieb Rory O'Farrell:
> When I use 4.2.0, running on Xubuntu 16.04.03, to open an existing .odt file 
> I get a small popup that informs me of "general error".  The file then opens 
> correctly; starting 4.2.0 in a terminal gives no diagnostic.  Opening Writer 
> from the start centre there is no such error message; I can generate a test 
> document, but when I save, again I get an error "Error saving the document 
> Tom: General Error".  However the file Tom.odt is actually saved (in spite of 
> the error message), and will reopen giving the above "general error" message,
>
> Opening an existing simple spreadsheet - a short list of description and 
> amount - I get a Yellow exclamation mark and "Not all attributes could be 
> read"; on dismissing this, the sheet opens correctly.
>
>
>  -- 
> Rory O'Farrell 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

4.2.0 minor errors

[Rory O'Farrell]

When I use 4.2.0, running on Xubuntu 16.04.03, to open an existing .odt file I 
get a small popup that informs me of "general error".  The file then opens 
correctly; starting 4.2.0 in a terminal gives no diagnostic.  Opening Writer 
from the start centre there is no such error message; I can generate a test 
document, but when I save, again I get an error "Error saving the document Tom: 
General Error".  However the file Tom.odt is actually saved (in spite of the 
error message), and will reopen giving the above "general error" message,

Opening an existing simple spreadsheet - a short list of description and amount 
- I get a Yellow exclamation mark and "Not all attributes could be read"; on 
dismissing this, the sheet opens correctly.


 -- 
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org