Re: c++17 : how to manage the dynamic specification exception issue?
Hi Arrigo > On 05/28/2024 8:48 PM WEST Arrigo Marchiori wrote: > IMHO we should just get rid of those "throw (...)" specifications. > > Roughly counted, there are 17,000 in header files only. > > If we get a bit of consensus, it may worth start opening pull request > to remove such specifications from the most relevant header files. > > What do others think? If it improves the code and it doesn't break anything, the answer is: Just Do It! ;) Best, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: c++17 : how to manage the dynamic specification exception issue?
Hello, On Sun, May 26, 2024 at 04:16:44PM +0200, SET wrote: > Hello, > > I'm trying to build a C++ application that requires AOO and libphonenumber. > The latter requires c++17, which does not accept AOO headers because of the > throw(...) statements in the function signatures. It builds with clang but > constantly fails with g++. > > Sample error message: > > openoffice4/sdk/include/com/sun/star/text/XTextCursor.hdl:29:57: error: > ISO > C++17 does not allow dynamic exception specifications > 29 | virtual void SAL_CALL gotoEnd( ::sal_Bool bExpand ) throw > (::com::sun::star::uno::RuntimeException) = 0; > > It's OK for me to go with clang, the unknown being 'How long will it build?'. > I just wish to know it there's some way to build with g++ also. IMHO we should just get rid of those "throw (...)" specifications. Roughly counted, there are 17,000 in header files only. If we get a bit of consensus, it may worth start opening pull request to remove such specifications from the most relevant header files. What do others think? -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
c++17 : how to manage the dynamic specification exception issue?
Hello, I'm trying to build a C++ application that requires AOO and libphonenumber. The latter requires c++17, which does not accept AOO headers because of the throw(...) statements in the function signatures. It builds with clang but constantly fails with g++. Sample error message: openoffice4/sdk/include/com/sun/star/text/XTextCursor.hdl:29:57: error: ISO C++17 does not allow dynamic exception specifications 29 | virtual void SAL_CALL gotoEnd( ::sal_Bool bExpand ) throw (::com::sun::star::uno::RuntimeException) = 0; It's OK for me to go with clang, the unknown being 'How long will it build?'. I just wish to know it there's some way to build with g++ also. A sample minimal code is attached if needed. Thank you for any input. <> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How do I sign up for Apache Open Office development contributor ?
Hi Chris, Am 03.11.22 um 22:56 schrieb chris deen: Hey thanks Peter I really appreciate it. At the risk of showing my ignorance I will say that if you can provide a link demonstrating what you mean by working with mailing list that would be a help. No problem, you are welcome. check out https://openoffice.apache.org/mailing-lists.html important for development is the dev mailing list you already communicate with. if you have questions or ideas feel free to share. btw. there is also a archive. check this mail from damjan: https://lists.apache.org/list?dev@openoffice.apache.org:lte=1M:expat maybe another nice starting point. Other than that I'm comfortable with GitHub and doing actual coding, of course. I look forward to working on the projects! I hope we can make more steps forward. On Thu, Nov 3, 2022, 5:45 PM Peter Kovacs wrote: Hi Chris, this is the right email mailing list. Do you know how to work with mailing lists? best way to hand in your work is through GitHub [1]. you can submit your work there for review. our priority list [2] how to build AOO [3] if you have questions just ask away... all the best Peter [1] https://github.com/apache/openoffice <https://github.com/apache/openoffice-org> [2] https://cwiki.apache.org/confluence/display/OOOUSERS/Blocker+issues+4.2.0 [3] https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO Am 03.11.22 um 22:11 schrieb chris deen: Hello! I am trying to locate the correct email address to get involved in working on Apache OpenOffice. I am trying to bring my C++ skills up to date and am looking for volunteer opportunities to do so. This sounds like the perfect way to do so! I followed the link from this page: https://www.openoffice.org/download/ image.png Thanks !
Re: How do I sign up for Apache Open Office development contributor ?
Hey thanks Peter I really appreciate it. At the risk of showing my ignorance I will say that if you can provide a link demonstrating what you mean by working with mailing list that would be a help. Other than that I'm comfortable with GitHub and doing actual coding, of course. I look forward to working on the projects! On Thu, Nov 3, 2022, 5:45 PM Peter Kovacs wrote: > Hi Chris, > > this is the right email mailing list. Do you know how to work with mailing > lists? > > best way to hand in your work is through GitHub [1]. you can submit your > work there for review. > > our priority list [2] > > how to build AOO [3] > > if you have questions just ask away... > > > all the best > > Peter > > [1] https://github.com/apache/openoffice > <https://github.com/apache/openoffice-org> > > [2] > https://cwiki.apache.org/confluence/display/OOOUSERS/Blocker+issues+4.2.0 > > [3] https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO > Am 03.11.22 um 22:11 schrieb chris deen: > > Hello! > I am trying to locate the correct email address to get involved in working > on Apache OpenOffice. I am trying to bring my C++ skills up to date and am > looking for volunteer opportunities to do so. This sounds like the perfect > way to do so! > > I followed the link from this page: > https://www.openoffice.org/download/ > > [image: image.png] > > > Thanks ! > > >
Re: How do I sign up for Apache Open Office development contributor ?
Hi Chris, this is the right email mailing list. Do you know how to work with mailing lists? best way to hand in your work is through GitHub [1]. you can submit your work there for review. our priority list [2] how to build AOO [3] if you have questions just ask away... all the best Peter [1] https://github.com/apache/openoffice [2] https://cwiki.apache.org/confluence/display/OOOUSERS/Blocker+issues+4.2.0 [3] https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO Am 03.11.22 um 22:11 schrieb chris deen: Hello! I am trying to locate the correct email address to get involved in working on Apache OpenOffice. I am trying to bring my C++ skills up to date and am looking for volunteer opportunities to do so. This sounds like the perfect way to do so! I followed the link from this page: https://www.openoffice.org/download/ image.png Thanks !
How do I sign up for Apache Open Office development contributor ?
Hello! I am trying to locate the correct email address to get involved in working on Apache OpenOffice. I am trying to bring my C++ skills up to date and am looking for volunteer opportunities to do so. This sounds like the perfect way to do so! I followed the link from this page: https://www.openoffice.org/download/ [image: image.png] Thanks !
Re: How to scale the Project
Hi Peter, I have often thought about starting some TODO type lists on the planning wiki but haven't had time yet. We may already have one somewhere. Besides the obvious 4.2 blockers, there are probably a number of things we could come up with divided by areas like main office development, QA, docs, infrastructure, etc. Like in QA there are a number of new tests that need done and a large project could be to update the framework JUnit from 4 to 5 for example. Maybe for areas or tasks we could and volunteers for mentors and tasks. Then we would have concrete things to point volunteers to by interest instead of letting them try to find things to work on on their own. When there is a volunteer maybe they feel a need to complete the task. After all that maybe a new call for volunteers? Just a thought. Best regards, Carl On 8/29/22 2:50 PM, Peter Kovacs wrote: Hi all, I had on the weekend a philosophical talk with a friend of mine. One Claim ha did in this discussion has been that (for whatever Reasons) not a lot of people have the trait of initiative. Having initiative is a special trait. Since we suffer from the Issue that there are people who would like to help, but not show any signs of Intiative, I thought we should maybe discuss how we could empower programmers to work on Issues. My friend suggested in the discussion that maybe it could work out that volunteers with initiative write what is to do in a specific case. And then we look for someone to do the task. This might be inefficient at first. But maybe we can get people to volunteer by this method. What do you think? Does anyone have experience from other Projects? And how much needxs to be layed out in order other volunteers look into it? Any thoughts? All the best Peter - 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
How to scale the Project
Hi all, I had on the weekend a philosophical talk with a friend of mine. One Claim ha did in this discussion has been that (for whatever Reasons) not a lot of people have the trait of initiative. Having initiative is a special trait. Since we suffer from the Issue that there are people who would like to help, but not show any signs of Intiative, I thought we should maybe discuss how we could empower programmers to work on Issues. My friend suggested in the discussion that maybe it could work out that volunteers with initiative write what is to do in a specific case. And then we look for someone to do the task. This might be inefficient at first. But maybe we can get people to volunteer by this method. What do you think? Does anyone have experience from other Projects? And how much needxs to be layed out in order other volunteers look into it? Any thoughts? All the best Peter - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to access UNO_CONSTANTS definitions via OLE/COM? (Re: Windows version: ProgIDs and typelibs for OLE/COM ?
Hi Andrew,
thank you *very* much indeed!
Your code gives much help already to save me a lot of research, so kudos to you! (E.g. from your
code it is clear that one can use the same code for fetching constant and enum values, which is
already very helpful per se!)
Will experiment a little bit before proceeding with the nutshell OLE/COM samples. Some abilities are
not directly available in the context, if a script is run outside of AOO using OLE/COM such as
GetDefaultContext(), however it is possible to fetch it from the service manager with
serviceManager.DefaultContext(). Or it would not be possible to reference the enum values for the
TypeClass in such a handy manner. However, it is very feasible to get at that information (and
others) one way or the other.
Again, thank you very much!
---rony
On 17.06.2022 15:31, Andrew Pitonyak wrote:
This is how I get the manager using Basic:
Get the type description manager from the default context; see section 10.4
Context, which also shows how to enumerate all of the singleton objects
available.
Function GetTypeDescriptionManager()
Dim sTDMName$ ' Name of the type description manager.
sTDMName = "/singletons/com.sun.star.reflection.theTypeDescriptionManager"
GetTypeDescriptionManager() = GetDefaultContext().getValueByName(sTDMName)
End Function
The following method enumerates all “things” in the com.sun.star.awt module.
Sub EnumerateTypesTest
Dim oTDM ' Type Description Manager.
Dim oTDE ' Type Description Enumerations.
Dim oTD ' One Type Description.
Dim typeArray ' Types for which descriptions are returned.
Dim s$ ' Utility string variable.
REM All supported types.
typeArray = Array(com.sun.star.uno.TypeClass.VOID, _
com.sun.star.uno.TypeClass.CHAR, _
com.sun.star.uno.TypeClass.BOOLEAN, _
com.sun.star.uno.TypeClass.BYTE, _
com.sun.star.uno.TypeClass.SHORT, _
com.sun.star.uno.TypeClass.UNSIGNED_SHORT, _
com.sun.star.uno.TypeClass.LONG, _
com.sun.star.uno.TypeClass.UNSIGNED_LONG, _
com.sun.star.uno.TypeClass.HYPER, _
com.sun.star.uno.TypeClass.UNSIGNED_HYPER, _
com.sun.star.uno.TypeClass.FLOAT, _
com.sun.star.uno.TypeClass.DOUBLE, _
com.sun.star.uno.TypeClass.STRING, _
com.sun.star.uno.TypeClass.TYPE, _
com.sun.star.uno.TypeClass.ANY, _
com.sun.star.uno.TypeClass.ENUM, _
com.sun.star.uno.TypeClass.TYPEDEF, _
com.sun.star.uno.TypeClass.STRUCT, _
com.sun.star.uno.TypeClass.UNION, _
com.sun.star.uno.TypeClass.EXCEPTION, _
com.sun.star.uno.TypeClass.SEQUENCE, _
com.sun.star.uno.TypeClass.ARRAY, _
com.sun.star.uno.TypeClass.INTERFACE, _
com.sun.star.uno.TypeClass.SERVICE, _
com.sun.star.uno.TypeClass.MODULE, _
com.sun.star.uno.TypeClass.INTERFACE_METHOD, _
com.sun.star.uno.TypeClass.INTERFACE_ATTRIBUTE, _
com.sun.star.uno.TypeClass.UNKNOWN, _
com.sun.star.uno.TypeClass.PROPERTY, _
com.sun.star.uno.TypeClass.CONSTANT, _
com.sun.star.uno.TypeClass.CONSTANTS, _
com.sun.star.uno.TypeClass.SINGLETON)
oTDM = GetTypeDescriptionManager()
Dim sBaseName$ : sBaseName = "com.sun.star.awt"
' Change com.sun.star.reflection.TypeDescriptionSearchDepth.ONE
' to com.sun.star.reflection.TypeDescriptionSearchDepth.INFINITE
' to traverse more than a single level.
oTDE = oTDM.createTypeDescriptionEnumeration(sBaseName, _
typeArray, _
com.sun.star.reflection.TypeDescriptionSearchDepth.ONE)
While oTDE.hasMoreElements()
oTD = oTDE.nextTypeDescription()
s$ = s & oTD.Name & CHR$(10)
Wend
MsgBox s
End Sub
To get the information on a specific fully qualified type, use the following
macro (adapted from an example by Bernard Marcelly):
Function GetOOoConst(constString)
Dim sTDMName$
Dim oTDM
sTDMName = "/singletons/com.sun.star.reflection.theTypeDescriptionManager"
oTDM = GetDefaultContext().getValueByName(sTDMName)
If oTDM.hasByHierarchicalName(constString) Then
GetOOoConst = oTDM.getByHierarchicalName(constString)
Else
MsgBox "Unrecognized name : " & constString, 16, "OOo API constant or enum"
End If
End Function
The method is usable to obtain constant and enumeration values from a text
string
Print GetOOoConst("com.sun.star.awt.FontSlant.ITALIC")
This can also return an object that describes the type. This can be used to
enumerate the values and the strings.
Sub EnumerateEnumerations(sName$)
Dim oTD ' One Type Description.
Dim oTDE ' Element enumeration
Dim s$ ' Utility string variable.
Dim sNames
Dim lValues
Dim i As Long
Dim iCount As Integer
oTD = GetOOoConst(sName)
If IsNull(oTD) OR IsEmpty(oTD) Then
Exit Sub
End If
If HasUnoInterfaces(oTD, "com.sun.star.reflection.X
Re: How to access UNO_CONSTANTS definitions via OLE/COM? (Re: Windows version: ProgIDs and typelibs for OLE/COM ?
This is how I get the manager using Basic:
Get the type description manager from the default context; see section 10.4
Context, which also shows how to enumerate all of the singleton objects
available.
Function GetTypeDescriptionManager()
Dim sTDMName$ ' Name of the type description manager.
sTDMName = "/singletons/com.sun.star.reflection.theTypeDescriptionManager"
GetTypeDescriptionManager() = GetDefaultContext().getValueByName(sTDMName)
End Function
The following method enumerates all “things” in the com.sun.star.awt module.
Sub EnumerateTypesTest
Dim oTDM ' Type Description Manager.
Dim oTDE ' Type Description Enumerations.
Dim oTD ' One Type Description.
Dim typeArray ' Types for which descriptions are returned.
Dim s$ ' Utility string variable.
REM All supported types.
typeArray = Array(com.sun.star.uno.TypeClass.VOID, _
com.sun.star.uno.TypeClass.CHAR, _
com.sun.star.uno.TypeClass.BOOLEAN, _
com.sun.star.uno.TypeClass.BYTE, _
com.sun.star.uno.TypeClass.SHORT, _
com.sun.star.uno.TypeClass.UNSIGNED_SHORT, _
com.sun.star.uno.TypeClass.LONG, _
com.sun.star.uno.TypeClass.UNSIGNED_LONG, _
com.sun.star.uno.TypeClass.HYPER, _
com.sun.star.uno.TypeClass.UNSIGNED_HYPER, _
com.sun.star.uno.TypeClass.FLOAT, _
com.sun.star.uno.TypeClass.DOUBLE, _
com.sun.star.uno.TypeClass.STRING, _
com.sun.star.uno.TypeClass.TYPE, _
com.sun.star.uno.TypeClass.ANY, _
com.sun.star.uno.TypeClass.ENUM, _
com.sun.star.uno.TypeClass.TYPEDEF, _
com.sun.star.uno.TypeClass.STRUCT, _
com.sun.star.uno.TypeClass.UNION, _
com.sun.star.uno.TypeClass.EXCEPTION, _
com.sun.star.uno.TypeClass.SEQUENCE, _
com.sun.star.uno.TypeClass.ARRAY, _
com.sun.star.uno.TypeClass.INTERFACE, _
com.sun.star.uno.TypeClass.SERVICE, _
com.sun.star.uno.TypeClass.MODULE, _
com.sun.star.uno.TypeClass.INTERFACE_METHOD, _
com.sun.star.uno.TypeClass.INTERFACE_ATTRIBUTE, _
com.sun.star.uno.TypeClass.UNKNOWN, _
com.sun.star.uno.TypeClass.PROPERTY, _
com.sun.star.uno.TypeClass.CONSTANT, _
com.sun.star.uno.TypeClass.CONSTANTS, _
com.sun.star.uno.TypeClass.SINGLETON)
oTDM = GetTypeDescriptionManager()
Dim sBaseName$ : sBaseName = "com.sun.star.awt"
' Change com.sun.star.reflection.TypeDescriptionSearchDepth.ONE
' to com.sun.star.reflection.TypeDescriptionSearchDepth.INFINITE
' to traverse more than a single level.
oTDE = oTDM.createTypeDescriptionEnumeration(sBaseName, _
typeArray, _
com.sun.star.reflection.TypeDescriptionSearchDepth.ONE)
While oTDE.hasMoreElements()
oTD = oTDE.nextTypeDescription()
s$ = s & oTD.Name & CHR$(10)
Wend
MsgBox s
End Sub
To get the information on a specific fully qualified type, use the following
macro (adapted from an example by Bernard Marcelly):
Function GetOOoConst(constString)
Dim sTDMName$
Dim oTDM
sTDMName = "/singletons/com.sun.star.reflection.theTypeDescriptionManager"
oTDM = GetDefaultContext().getValueByName(sTDMName)
If oTDM.hasByHierarchicalName(constString) Then
GetOOoConst = oTDM.getByHierarchicalName(constString)
Else
MsgBox "Unrecognized name : " & constString, 16, "OOo API constant or enum"
End If
End Function
The method is usable to obtain constant and enumeration values from a text
string
Print GetOOoConst("com.sun.star.awt.FontSlant.ITALIC")
This can also return an object that describes the type. This can be used to
enumerate the values and the strings.
Sub EnumerateEnumerations(sName$)
Dim oTD ' One Type Description.
Dim oTDE ' Element enumeration
Dim s$ ' Utility string variable.
Dim sNames
Dim lValues
Dim i As Long
Dim iCount As Integer
oTD = GetOOoConst(sName)
If IsNull(oTD) OR IsEmpty(oTD) Then
Exit Sub
End If
If HasUnoInterfaces(oTD, "com.sun.star.reflection.XEnumTypeDescription") Then
'MsgBox Join( oTD.getEnumNames(), CHR$(10))
sNames = oTD.getEnumNames()
lValues = otd.getEnumValues()
For i = LBound(sNames) To UBound(sNames)
iCount = iCount + 1
If (iCount > 40) Then
MsgBox(s)
s = ""
End If
s = s & lValues(i) & CHR$(9) & sNames(i) & CHR$(10)
Next
ElseIf HasUnoInterfaces(oTD,
"com.sun.star.reflection.XConstantsTypeDescription") Then
lValues = oTD.getConstants()
For i = LBound(lValues) To UBound(lValues)
iCount = iCount + 1
If (iCount > 40) Then
MsgBox(s)
s = ""
End If
s = s & lValues(i).getConstantValue() & CHR$(9) & lValues(i).getName() &
CHR$(10)
Next
Else
'Inspect oTD
MsgBox "Unsupported type " & sName
Exit Sub
End If
MsgBox s
End Sub
This can be used to se
Re: How to access UNO_CONSTANTS definitions via OLE/COM? (Re: Windows version: ProgIDs and typelibs for OLE/COM ?
OK, it is possible using "/singletons/com.sun.star.reflection.theTypeDescriptionManager". (Will have
to look further into it to maybe use it also for UNO_ENUM and the like.)
---rony
On 17.06.2022 12:46, Rony G. Flatscher wrote:
In the process of creating a few nutshell examples using OLE/COM.
One open problem is how to get to the UNO_CONSTANTS via the OLE/COM bridge. Here a snippet and its
output (the tilde is the message operator in ooRexx and could be replaced by a dot for JScript and
the like; .nil is the singleton object with the string value "The NIL object" to represent null):
factory = .OLEObject~new('com.sun.star.ServiceManager')
coreReflection =
factory~createInstance("com.sun.star.reflection.CoreReflection")
clzName="com.sun.star.table.CellHoriJustify"
say clzName":" "(UNO_ENUM)"
type=coreReflection~forName(clzName)
say "type:" type "type~getName:" type~getname "(forName)"
do f over type~getFields -- iterate over all fields
say f~getName":" f~get(.nil) -- show name and get the value
end
say
type=coreReflection~getType(clzName)
say "type:" type "type~getName:" type~getname "(getType)"
say "-"~copies(79)
say
clzName="com.sun.star.awt.FontWeight"
say clzName":" "(UNO_CONSTANTS)"
type=coreReflection~forName(clzName)
say "type:" type "(forName)"
say
type=coreReflection~getType(clzName)
say "type:" type "type~getName:" type~getname "(getType)"
The output is:
com.sun.star.table.CellHoriJustify: (UNO_ENUM)
type: an OLEObject type~getName: com.sun.star.table.CellHoriJustify (forName)
STANDARD: 0
LEFT: 1
CENTER: 2
RIGHT: 3
BLOCK: 4
REPEAT: 5
type: an OLEObject type~getName: string (getType)
---
com.sun.star.awt.FontWeight: (UNO_CONSTANTS)
type: The NIL object (forName)
type: an OLEObject type~getName: string (getType)
So using CoreReflection does not allow one to reflect UNO_CONSTANTS (forName()
returns null).
Using getType() will return "string" for both, UNO_ENUM and UNO_CONSTANTS.
---
Would anyone have an idea how to use OLE/COM to get at the fields and values for UNO_CONSTANTS
like FontWeight (getting the UNO_CONSTANT value for BOLD other than manually via
<https://www.openoffice.org/api/docs/common/ref/com/sun/star/awt/FontWeight.html>)?
---rony
P.S.: In the process of creating OLE/COM nutshell examples for scalc, swriter and simpress.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
How to access UNO_CONSTANTS definitions via OLE/COM? (Re: Windows version: ProgIDs and typelibs for OLE/COM ?
In the process of creating a few nutshell examples using OLE/COM.
One open problem is how to get to the UNO_CONSTANTS via the OLE/COM bridge. Here a snippet and its
output (the tilde is the message operator in ooRexx and could be replaced by a dot for JScript and
the like; .nil is the singleton object with the string value "The NIL object" to represent null):
factory= .OLEObject~new('com.sun.star.ServiceManager')
coreReflection =
factory~createInstance("com.sun.star.reflection.CoreReflection")
clzName="com.sun.star.table.CellHoriJustify"
say clzName":" "(UNO_ENUM)"
type=coreReflection~forName(clzName)
say "type:" type "type~getName:" type~getname "(forName)"
do f over type~getFields -- iterate over all fields
say f~getName":" f~get(.nil) -- show name and get the value
end
say
type=coreReflection~getType(clzName)
say "type:" type "type~getName:" type~getname "(getType)"
say "-"~copies(79)
say
clzName="com.sun.star.awt.FontWeight"
say clzName":" "(UNO_CONSTANTS)"
type=coreReflection~forName(clzName)
say "type:" type "(forName)"
say
type=coreReflection~getType(clzName)
say "type:" type "type~getName:" type~getname "(getType)"
The output is:
com.sun.star.table.CellHoriJustify: (UNO_ENUM)
type: an OLEObject type~getName: com.sun.star.table.CellHoriJustify (forName)
STANDARD: 0
LEFT: 1
CENTER: 2
RIGHT: 3
BLOCK: 4
REPEAT: 5
type: an OLEObject type~getName: string (getType)
---
com.sun.star.awt.FontWeight: (UNO_CONSTANTS)
type: The NIL object (forName)
type: an OLEObject type~getName: string (getType)
So using CoreReflection does not allow one to reflect UNO_CONSTANTS (forName()
returns null).
Using getType() will return "string" for both, UNO_ENUM and UNO_CONSTANTS.
---
Would anyone have an idea how to use OLE/COM to get at the fields and values for UNO_CONSTANTS like
FontWeight (getting the UNO_CONSTANT value for BOLD other than manually via
<https://www.openoffice.org/api/docs/common/ref/com/sun/star/awt/FontWeight.html>)?
---rony
P.S.: In the process of creating OLE/COM nutshell examples for scalc, swriter
and simpress.
Re: How to get debug information (Java, oxt)
Hi Rony, Am 06.06.22 um 16:07 schrieb Rony G. Flatscher (Apache): Hi Peter, thank you very much for coming back to this! A pleasure. If you would be aware of such examples I would be grateful for any links. I am sorry. I have no clue. I wanted to get the discussion started, and just did a classic consultant Bullshit bingo move. Which sometimes helps to get on the road to the real solution. So I hoped it worked by catching Carls attention. However I will have look when I find time. Maybe I come back to this once I started with my "getting rid of the assembler code" - project :-D Again, thank you very much for taking time for this! you are welcome. All the best Peter ---rony On 6/4/2022 7:40 AM, Peter Kovacs wrote: I going through old emails and no one seems to answer you. Can you describe your setup? OS, have you sdk installed? All the best Peter Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Carl, On 6/7/2022 12:07 AM, Carl Marcum wrote: Hi Rony, On 6/6/22 10:15 AM, Rony G. Flatscher (Apache) wrote: Hi Carl, On 6/4/2022 3:31 PM, Carl Marcum wrote: ... cut ... Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? Yes. For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Thank you very much for this hint! Are you using the --verbose option when using unopkg from the command line? Yes. As mentioned in the other reply, one of my problems is that in order to quickly get (re-)adjusted to this infrastructure (being away because of other efforts for quite some time in between activities) I would need some short, functional examples (like a nutshell extension in Java with proper packaging to become able to experiment with both, the Java code and the packaging, hoping to develop a conceptual model by doing so). It may be the case that these samples exist, but that I have not found them. So any hint or link to such (Java) nutshell examples would be great as they probably help a lot getting afloat quickly. It might be a larger example that what you're looking for but take a look at my openoffice-groovy project [1] that adds Apache Groovy as a macro language. There is also an OXT on the extensions site [2]. Thank you very much, indeed! As a matter of fact, like yourself I used the BeanShell example to add ooRexx as a macro extension. Nevertheless I will look into it (in the middle of July when things have settled down a little bit around here), as I might learn how to install the macros in share and user space (doing this "manually" currently). [On the side: my premiere platform for this has been AOO, but because of the students I have been also trying to allow for using ooRexx as a macro language also for LO. It seems that LO has changed too much to allow that to be still the case, which is awkward. Short of time I am not able to pursue that, as the platform defining OO is AOO only.] If you would rather have an basic stripped down extension example I can generate you one from my templates or guide you in setting up so you can generate your own addons and addins. [1] https://github.com/cbmarcum/openoffice-groovy [2] https://extensions.openoffice.org/en/project/groovy-scripting-openoffice That is *very* kind of you and I would like to pick up your offer about samples that would show/demonstrate/guide to become able to create/generate also own addons and addins in ooRexx (this is something I have been thinking of for quite some time)! Probably only a brief sample/pattern for an addon and an addin and what the relevant definitions would be terrific (especially what has to be taken into account for registering) and maybe where to find the relevant documentation! Groovy and/or Java would be more than fine! Best regards ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Rony, On 6/6/22 10:15 AM, Rony G. Flatscher (Apache) wrote: Hi Carl, On 6/4/2022 3:31 PM, Carl Marcum wrote: ... cut ... Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? Yes. For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Thank you very much for this hint! Are you using the --verbose option when using unopkg from the command line? Yes. As mentioned in the other reply, one of my problems is that in order to quickly get (re-)adjusted to this infrastructure (being away because of other efforts for quite some time in between activities) I would need some short, functional examples (like a nutshell extension in Java with proper packaging to become able to experiment with both, the Java code and the packaging, hoping to develop a conceptual model by doing so). It may be the case that these samples exist, but that I have not found them. So any hint or link to such (Java) nutshell examples would be great as they probably help a lot getting afloat quickly. It might be a larger example that what you're looking for but take a look at my openoffice-groovy project [1] that adds Apache Groovy as a macro language. There is also an OXT on the extensions site [2]. If you would rather have an basic stripped down extension example I can generate you one from my templates or guide you in setting up so you can generate your own addons and addins. [1] https://github.com/cbmarcum/openoffice-groovy [2] https://extensions.openoffice.org/en/project/groovy-scripting-openoffice Best regards, Carl ---rony - 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: How to get debug information (Java, oxt)
Hi Carl, On 6/4/2022 3:31 PM, Carl Marcum wrote: ... cut ... Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? Yes. For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Thank you very much for this hint! Are you using the --verbose option when using unopkg from the command line? Yes. As mentioned in the other reply, one of my problems is that in order to quickly get (re-)adjusted to this infrastructure (being away because of other efforts for quite some time in between activities) I would need some short, functional examples (like a nutshell extension in Java with proper packaging to become able to experiment with both, the Java code and the packaging, hoping to develop a conceptual model by doing so). It may be the case that these samples exist, but that I have not found them. So any hint or link to such (Java) nutshell examples would be great as they probably help a lot getting afloat quickly. ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Peter,
thank you very much for coming back to this!
I do not have the SDK installed. Unfortunately, the exact details have escaped me since (having done
too many other things in between).
Background: many, many years ago I have authored a bridge for the scripting language ooRexx taking
advantage of the AOO scripting framework which is Java based. Basically I copied the BeanShell
engine (editor and dispatching the scripts) and adjusted it for ooRexx (is C++ but there is a Java
bridge). The packaging was done copying some other samples, but could get it done only after
receiving help from some developers back then who knew about the uno packaging process and what the
xml configuration files need to contain. (Also, I reverse-engineered the file layout for scripting
language scripts in order to place ooRexx samples there.)
So my problem in essence is lack of knowledge of how to properly debug Java code in this context
when the Java exceptions are not carried over and displayed. Also, I have no real working knowledge
of how one could/should go about configuring uno packages.
It would be of great help if there was (and maybe there is, yet, not found so far) a minimal, but
working ("nutshell") Java example that would demonstrate and briefly explain how to create an uno
package in Java, being able to deploy it (maybe with a method/function that returns "hello, world
from a Java uno extension") and explaining the minimal configuration definitions.
If you would be aware of such examples I would be grateful for any links.
Again, thank you very much for taking time for this!
---rony
On 6/4/2022 7:40 AM, Peter Kovacs wrote:
I going through old emails and no one seems to answer you.
Can you describe your setup? OS, have you sdk installed?
All the best
Peter
Am 03.10.21 um 15:12 schrieb Rony G. Flatscher:
Searched on the Internet but found no pointers so asking here.
Problem: something goes wrong while registering a Java based extension (an oxt
), but no information
is supplied.
Question: how to get debug (logging) information from a Java based extension?
Maybe with a Java
stacktrace?
---rony
P.S.: Could find the cause in the oxt, but this was really quite time consuming
(and therefore
effortful). Some new Java code caused a Runtime exception such that the
registering of the oxt could
not conclude; it would have helped a lot, if the Runtime exception was supplied
rather an empty
message was given (using unopkg from the commandline).
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
Hi Rony, On 6/4/22 1:40 AM, Peter Kovacs wrote: I going through old emails and no one seems to answer you. Can you describe your setup? OS, have you sdk installed? All the best Peter Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). So the error is during unopkg and not when using the installed extension correct? For runtime errors on Linux I start the office from the command line and you can println output to it from the extension. Are you using the --verbose option when using unopkg from the command line? Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to get debug information (Java, oxt)
I going through old emails and no one seems to answer you. Can you describe your setup? OS, have you sdk installed? All the best Peter Am 03.10.21 um 15:12 schrieb Rony G. Flatscher: Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). - 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: How to delete a wrong email list subscription?
Hello Dave, > -Original Message- > From: Dave [mailto:b...@apache.org] > Sent: Thursday, November 04, 2021 9:07 AM > To: dev@openoffice.apache.org > Subject: Re: How to delete a wrong email list subscription? > Contact the list moderator(s) users-de-ow...@openoffice.apache.org > They have the facilities to resolve this issue. All right, I will do that. (But the moderator should have known by now anyway, because the problems have been going on for a few weeks). greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to delete a wrong email list subscription?
On 04/11/2021 07:41, Jörg Schmidt wrote: > > Hello, > > For some time now, there have been spam emails on > users...@openoffice.apache.org _which appear_ to be sent by a registered > spammer who is misusing the email address of a third party. > > Questions: > How can I reliably check whether the address "i...@dkb.de" is actually > registered for the list mentioned (users...@openoffice.apache.org)? > How can we remove the registration of this email (i...@dkb.de)? > > > > greetings, > Jörg > > P.S. > I'm not the moderator of users...@openoffice.apache.org, but I think someone > needs to address this issue. Hi Jörg, Contact the list moderator(s) users-de-ow...@openoffice.apache.org They have the facilities to resolve this issue. Regards Dave - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How to delete a wrong email list subscription?
Hello, For some time now, there have been spam emails on users...@openoffice.apache.org _which appear_ to be sent by a registered spammer who is misusing the email address of a third party. Questions: How can I reliably check whether the address "i...@dkb.de" is actually registered for the list mentioned (users...@openoffice.apache.org)? How can we remove the registration of this email (i...@dkb.de)? greetings, Jörg P.S. I'm not the moderator of users...@openoffice.apache.org, but I think someone needs to address this issue. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How to get debug information (Java, oxt)
Searched on the Internet but found no pointers so asking here. Problem: something goes wrong while registering a Java based extension (an oxt ), but no information is supplied. Question: how to get debug (logging) information from a Java based extension? Maybe with a Java stacktrace? ---rony P.S.: Could find the cause in the oxt, but this was really quite time consuming (and therefore effortful). Some new Java code caused a Runtime exception such that the registering of the oxt could not conclude; it would have helped a lot, if the Runtime exception was supplied rather an empty message was given (using unopkg from the commandline). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: How to recruit [Was: Feature: automatic enter of a decimal point at a fixed position]
Hello Arrigo, > -Original Message- > From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] > Sent: Friday, April 30, 2021 1:30 PM > To: dev@openoffice.apache.org > Subject: Re: How to recruit [Was: Feature: automatic enter of > a decimal point at a fixed position] > > Where can I find an archive of this list so I can look at it? > > The list was recently renamed, therefore the archives are > split in two. > > New list: > http://mail-archives.apache.org/mod_mbox/openoffice-volunteer/ > Old list: > http://mail-archives.apache.org/mod_mbox/openoffice-recruitment/ thank you > > > If so, I would appreciate your (possibly constructive :-) > criticism, > > > as I tried to reply to a couple of people but I do not > seem to have > > > had any success so far. > > > > My, described, personal experiences come from the time of > OOo [!], the problem was then, however, almost identical to > the situation today: > > Too many experienced people don't understand that > newcomers, who have no FOSS project experience, don't > understand the meritocratic way of working and therefore > misunderstand the liberal request 'find yourself the part of > the project you want to work on' as 'I don't feel like giving > you concrete help'. > > > > It is our mistake to pretend to deprive the newcomers of > their freedom, only if we assign them concrete work. And I > name this mistake by saying that we raise the tool (!) > "meritocracy" to the status of a religion. > > I agree that an initial bit of guidance is useful, but I am not > sure I understand your very last point. I'm afraid you don't understand my complete statement, because the first part is not specifically about guidance, but about assigning tasks. You should not misunderstand "assigning tasks" as giving orders, but as the way experienced project members give advice on which tasks they should start with. What is regularly done, however, is something different, namely telling the newcomers to choose for themselves what they want to do (in the 'tone of voice' 'they MUST choose for themselves what they want to do'). And this happens out of the schematism that some think that any steering of the interests of newcomers would already run counter to the idea of meritocracy. And this view I called "religion", you can also call it "dogmatic", in any case it harms the project. I give an example: Peter's answer ([1]) to [2] was undoubtedly friendly, but it was general and without concrete benefits for a newcomer, who actually wants one thing above all: he initial wants to do something concrete and thereby get to know the project. What did I do? I invited Fabio to the ProOO-box (www.prooo-box.org) and told him specifically where we need help and explained to him what he must consider and how he must proceed if he wants to follow our request. This means that I gave Fabio a concrete path for his first steps in the project. It doesn't mean that Fabio has to follow my suggestion, but probably he will do it voluntarily, because he is happy to know that he is doing something useful for the project. [1] http://mail-archives.apache.org/mod_mbox/openoffice-dev-de/202103.mbox/%3C343ed415-9307-c63a-bd9d-ac80ca2689b1%40apache.org%3E [2] http://mail-archives.apache.org/mod_mbox/openoffice-volunteer/202103.mbox/%3C001201d71e34%24542fcb30%24fc8f6190%24%40holdoffice.com%3E greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to recruit [Was: Feature: automatic enter of a decimal point at a fixed position]
Hello Jörg, On Fri, Apr 30, 2021 at 10:00:05AM +0200, Jörg Schmidt wrote: > Hello, > > > -Original Message- > > From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] > > Sent: Friday, April 30, 2021 8:13 AM > > To: dev@openoffice.apache.org > > Subject: How to recruit [Was: Feature: automatic enter of a > > decimal point at a fixed position] > > > Are you subscribed to the recruitment - volunteering list? > > No, I'm not. > > Where can I find an archive of this list so I can look at it? The list was recently renamed, therefore the archives are split in two. New list: http://mail-archives.apache.org/mod_mbox/openoffice-volunteer/ Old list: http://mail-archives.apache.org/mod_mbox/openoffice-recruitment/ > > If so, I would appreciate your (possibly constructive :-) criticism, > > as I tried to reply to a couple of people but I do not seem to have > > had any success so far. > > My, described, personal experiences come from the time of OOo [!], the > problem was then, however, almost identical to the situation today: > Too many experienced people don't understand that newcomers, who have no FOSS > project experience, don't understand the meritocratic way of working and > therefore misunderstand the liberal request 'find yourself the part of the > project you want to work on' as 'I don't feel like giving you concrete help'. > > It is our mistake to pretend to deprive the newcomers of their freedom, only > if we assign them concrete work. And I name this mistake by saying that we > raise the tool (!) "meritocracy" to the status of a religion. I agree that an initial bit of guidance is useful, but I am not sure I understand your very last point. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: How to recruit [Was: Feature: automatic enter of a decimal point at a fixed position]
Hello, > -Original Message- > From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] > Sent: Friday, April 30, 2021 8:13 AM > To: dev@openoffice.apache.org > Subject: How to recruit [Was: Feature: automatic enter of a > decimal point at a fixed position] > Are you subscribed to the recruitment - volunteering list? No, I'm not. Where can I find an archive of this list so I can look at it? > If so, I would appreciate your (possibly constructive :-) criticism, > as I tried to reply to a couple of people but I do not seem to have > had any success so far. My, described, personal experiences come from the time of OOo [!], the problem was then, however, almost identical to the situation today: Too many experienced people don't understand that newcomers, who have no FOSS project experience, don't understand the meritocratic way of working and therefore misunderstand the liberal request 'find yourself the part of the project you want to work on' as 'I don't feel like giving you concrete help'. It is our mistake to pretend to deprive the newcomers of their freedom, only if we assign them concrete work. And I name this mistake by saying that we raise the tool (!) "meritocracy" to the status of a religion. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How to recruit [Was: Feature: automatic enter of a decimal point at a fixed position]
Hello Jörg, All, On Fri, Apr 30, 2021 at 07:43:35AM +0200, Jörg Schmidt wrote: > > -Original Message- > > From: Peter Kovacs [mailto:pe...@apache.org] > > Sent: Thursday, April 29, 2021 10:32 PM > > To: dev@openoffice.apache.org > > Subject: Re: Feature: automatic enter of a decimal point at a > > fixed position > > > > If we want to attract people who are not yet sure if they > > want to work permanently, I'm afraid we have to find ways to > > make it even easier to get involved. > > +1, lowering the barrier is hard. > > Well, it may be laborious to overcome the hurdles, but it is not difficult. > One way would be for someone to feel responsible for the newcomers and give > them concrete support in their first steps in the project. But I've been > having this discussion for 15 years now, and it's regularly put down by the > fact that such support for newcomers would potentially be interference. > > e.g. I personally would never have found my way to OpenOffice if I had been > fobbed off as a newcomer by being told I have free choice in what I want to > do - no, I owe my being here to people like Andre, Thomas or Eric who had the > right human feeling to give me hints at the beginning which tasks would be > suitable for me. Are you subscribed to the recruitment - volunteering list? If so, I would appreciate your (possibly constructive :-) criticism, as I tried to reply to a couple of people but I do not seem to have had any success so far. This invitation is also valid for anyone would like to help, of course. I believe it's better to talk publicly on this list, but I could also accept private messages on this topic. Thank you in advance and best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Priority Issues: (was: How to cope with duplicate attributes in XML tags )
Sure pick one. No issues I have wrote more on purpose. Am 22. Februar 2021 18:53:02 MEZ schrieb Arrigo Marchiori : >Hello Peter, > >thank you very much for replying. > >On Sun, Feb 21, 2021 at 01:40:15AM +0100, Peter Kovacs wrote: > >> I would like to answer the priority list first. >> >> Currently I have following Issues on my mind. The list may not be >complete >> or others may have other Opinions, which is fine. >> >> >> On 07.02.21 21:51, Arrigo Marchiori wrote: >> > If we approve it, I will surely need your indication (as per a >> > previous thread on this ML) about the next "high priority issue" to >> > address. >> >> Next: >> >> File corruption: >> >> https://bz.apache.org/ooo/show_bug.cgi?id=126846 and >> https://forum.openoffice.org/en/forum/viewtopic.php?f=7=1532 > >I'm starting with the related report >https://bz.apache.org/ooo/show_bug.cgi?id=126869 >There are too many and... I have to choose one ;-) > >Best regards, >-- >Arrigo > >http://rigo.altervista.org > >- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Re: Priority Issues: (was: How to cope with duplicate attributes in XML tags )
Hello Peter, thank you very much for replying. On Sun, Feb 21, 2021 at 01:40:15AM +0100, Peter Kovacs wrote: > I would like to answer the priority list first. > > Currently I have following Issues on my mind. The list may not be complete > or others may have other Opinions, which is fine. > > > On 07.02.21 21:51, Arrigo Marchiori wrote: > > If we approve it, I will surely need your indication (as per a > > previous thread on this ML) about the next "high priority issue" to > > address. > > Next: > > File corruption: > > https://bz.apache.org/ooo/show_bug.cgi?id=126846 and > https://forum.openoffice.org/en/forum/viewtopic.php?f=7=1532 I'm starting with the related report https://bz.apache.org/ooo/show_bug.cgi?id=126869 There are too many and... I have to choose one ;-) Best regards, -- Arrigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Priority Issues: (was: How to cope with duplicate attributes in XML tags )
On 2/20/2021 7:40 PM, Peter Kovacs wrote: > I would like to answer the priority list first. > > Currently I have following Issues on my mind. The list may not be > complete or others may have other Opinions, which is fine. > > > On 07.02.21 21:51, Arrigo Marchiori wrote: >> If we approve it, I will surely need your indication (as per a >> previous thread on this ML) about the next "high priority issue" to >> address. > > Next: > > File corruption: > > https://bz.apache.org/ooo/show_bug.cgi?id=126846 and > https://forum.openoffice.org/en/forum/viewtopic.php?f=7=1532 > > > next 4.2.0 Issues: > > My filter in bugzilla points to: > https://bz.apache.org/ooo/buglist.cgi?cmdtype=runnamed_id=247426=4.2.0%20OpenIssues > > > Maybe someone else has a better list. > > > next: > > Patches we have received and we need to integrate: > > https://issues.apache.org/jira/browse/OPENOFFICE-45 > > > > Next: > > would be issues with corrupted profile files. > > This seem to be still a thing. I found these Issues: > > https://bz.apache.org/ooo/show_bug.cgi?id=121930 > > https://bz.apache.org/ooo/show_bug.cgi?id=121625 > > > Next: > > Windows: > > https://issues.apache.org/jira/browse/OPENOFFICE-35 > > > Next: > > Handling of other crashes: > https://issues.apache.org/jira/browse/OPENOFFICE-3 > > https://bz.apache.org/ooo/show_bug.cgi?id=125006 > > > > Issues with the extension manager: > > https://bz.apache.org/ooo/show_bug.cgi?id=127520 > > https://bz.apache.org/ooo/show_bug.cgi?id=122297 > > > Issues that deal with Memory leaks > > https://issues.apache.org/jira/browse/OPENOFFICE-28 > > (Currently only one) > > Peter; Your link comes back as does not exist from Bugzilla. The following 2 links are set as share with registered users and should work for anyone with a Bugzilla account. https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem=run=4.2.0_ReleaseBlockers https://bz.apache.org /ooo/buglist.cgi?cmdtype=dorem=run=4.2.0Milestone Regards Keith signature.asc Description: OpenPGP digital signature
Priority Issues: (was: How to cope with duplicate attributes in XML tags )
I would like to answer the priority list first. Currently I have following Issues on my mind. The list may not be complete or others may have other Opinions, which is fine. On 07.02.21 21:51, Arrigo Marchiori wrote: If we approve it, I will surely need your indication (as per a previous thread on this ML) about the next "high priority issue" to address. Next: File corruption: https://bz.apache.org/ooo/show_bug.cgi?id=126846 and https://forum.openoffice.org/en/forum/viewtopic.php?f=7=1532 next 4.2.0 Issues: My filter in bugzilla points to: https://bz.apache.org/ooo/buglist.cgi?cmdtype=runnamed_id=247426=4.2.0%20OpenIssues Maybe someone else has a better list. next: Patches we have received and we need to integrate: https://issues.apache.org/jira/browse/OPENOFFICE-45 Next: would be issues with corrupted profile files. This seem to be still a thing. I found these Issues: https://bz.apache.org/ooo/show_bug.cgi?id=121930 https://bz.apache.org/ooo/show_bug.cgi?id=121625 Next: Windows: https://issues.apache.org/jira/browse/OPENOFFICE-35 Next: Handling of other crashes: https://issues.apache.org/jira/browse/OPENOFFICE-3 https://bz.apache.org/ooo/show_bug.cgi?id=125006 Issues with the extension manager: https://bz.apache.org/ooo/show_bug.cgi?id=127520 https://bz.apache.org/ooo/show_bug.cgi?id=122297 Issues that deal with Memory leaks https://issues.apache.org/jira/browse/OPENOFFICE-28 (Currently only one) -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with duplicate attributes in XML tags
On 2/7/2021 10:22 AM, Arrigo Marchiori wrote: > Hello all, > > re-replying to Jim's message. > > On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote: > >> Funny that you bring this up... I'm been tracking down some bugs and they >> all seem to be XML related... fastsax->libwriterfilter with occasional cores >> due to __cxa_call_unexpected. >> >> I feel that making AOO more fragile by trying to work around cases where >> invalid and/or non-compliant XML is encountered is just wrong. We should >> either ignore the error (catch it) or raise an exception. Invalid data >> shouldn't >> be tolerated. Additionally, trying to be "lenient" is an easy vector for >> vulnerabilities. > > For the record: the detection of duplicated attributes is made > internally by the expat library. Our code just receives the error > message and cannot do anything to recover it. > > I don't believe it's worth patching expat to allow duplicated > attributes. I don't know the library well and I fear about the > consequences of tinkering with it. > > But then my question becomes: do we want to offer any data recovery > tools for corrupted documents? Like ``dumb'' XML parsers that just > shave away XML errors? > > 1- it could be an external tool, written in a language that is easier > to code into? (like Python, Perl, Java... whatever) > > 2- or an internal pre-parsing phase? It should not be based on the > expat library though; do we have any other possibilities among the > current modules? > > 3- or we leave it to hand-crafting by knowledgeable people on the > forum, as it is happening now? > > I am looking forward to opinions ... and possibily reviews of PR 122 > please ;-) > > Best regards, > Purely from a users point of view I agree with Jim. It should not be allowed to happen. Asking the user to run an external program, our to send it to the forum to be hand edit is a recipe for disaster to our user base and from a marketing standpoint. I could see an external program as a short term, stop gap work around. However it should only be that. Regards Keith signature.asc Description: OpenPGP digital signature
Re: How to cope with duplicate attributes in XML tags
Hello Peter, and thank you for taking time to reply. On Sun, Feb 07, 2021 at 04:58:19PM +0100, Peter Kovacs wrote: > Hello, > > On 07.02.21 16:22, Arrigo Marchiori wrote: > > Hello all, > > > > re-replying to Jim's message. > > > > On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote: > > > > > Funny that you bring this up... I'm been tracking down some bugs and they > > > all seem to be XML related... fastsax->libwriterfilter with occasional > > > cores > > > due to __cxa_call_unexpected. > > > > > > I feel that making AOO more fragile by trying to work around cases where > > > invalid and/or non-compliant XML is encountered is just wrong. We should > > > either ignore the error (catch it) or raise an exception. Invalid data > > > shouldn't > > > be tolerated. Additionally, trying to be "lenient" is an easy vector for > > > vulnerabilities. > > For the record: the detection of duplicated attributes is made > > internally by the expat library. Our code just receives the error > > message and cannot do anything to recover it. > > I think it is not an issue of expat itself. It is an issue of how expat is > setup. > > From the pure xml lore you can allow multiple elements of the same name. > > consider unordered HTML List, as a reference. I may have explained myself wrong... I am not talking about duplicated _elements_ but rather duplicated _attributes_. To remain in your example, the problem is not having multiple elements, but rather something like: [...] > We could provide a helper to help the user to figure out what has happened > maybe. By "helper" do you mean a separate program or a function inside AOO? [..] > > I am looking forward to opinions ... and possibily reviews of PR 122 > > please ;-) > I plan to have a look! Many thanks! If we approve it, I will surely need your indication (as per a previous thread on this ML) about the next "high priority issue" to address. Best regards, -- Arrigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with duplicate attributes in XML tags
Hello, On 07.02.21 16:22, Arrigo Marchiori wrote: Hello all, re-replying to Jim's message. On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote: Funny that you bring this up... I'm been tracking down some bugs and they all seem to be XML related... fastsax->libwriterfilter with occasional cores due to __cxa_call_unexpected. I feel that making AOO more fragile by trying to work around cases where invalid and/or non-compliant XML is encountered is just wrong. We should either ignore the error (catch it) or raise an exception. Invalid data shouldn't be tolerated. Additionally, trying to be "lenient" is an easy vector for vulnerabilities. For the record: the detection of duplicated attributes is made internally by the expat library. Our code just receives the error message and cannot do anything to recover it. I think it is not an issue of expat itself. It is an issue of how expat is setup. From the pure xml lore you can allow multiple elements of the same name. consider unordered HTML List, as a reference. I would opt for checking if we could allow that this Element can be read as a duplicate. The user can then delete the entry he does not like, and fix therefore the document. We could provide a helper to help the user to figure out what has happened maybe. I don't believe it's worth patching expat to allow duplicated attributes. I don't know the library well and I fear about the consequences of tinkering with it. But then my question becomes: do we want to offer any data recovery tools for corrupted documents? Like ``dumb'' XML parsers that just shave away XML errors? 1- it could be an external tool, written in a language that is easier to code into? (like Python, Perl, Java... whatever) 2- or an internal pre-parsing phase? It should not be based on the expat library though; do we have any other possibilities among the current modules? 3- or we leave it to hand-crafting by knowledgeable people on the forum, as it is happening now? I am looking forward to opinions ... and possibily reviews of PR 122 please ;-) I plan to have a look! Best regards, -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with duplicate attributes in XML tags
Hello all, re-replying to Jim's message. On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote: > Funny that you bring this up... I'm been tracking down some bugs and they > all seem to be XML related... fastsax->libwriterfilter with occasional cores > due to __cxa_call_unexpected. > > I feel that making AOO more fragile by trying to work around cases where > invalid and/or non-compliant XML is encountered is just wrong. We should > either ignore the error (catch it) or raise an exception. Invalid data > shouldn't > be tolerated. Additionally, trying to be "lenient" is an easy vector for > vulnerabilities. For the record: the detection of duplicated attributes is made internally by the expat library. Our code just receives the error message and cannot do anything to recover it. I don't believe it's worth patching expat to allow duplicated attributes. I don't know the library well and I fear about the consequences of tinkering with it. But then my question becomes: do we want to offer any data recovery tools for corrupted documents? Like ``dumb'' XML parsers that just shave away XML errors? 1- it could be an external tool, written in a language that is easier to code into? (like Python, Perl, Java... whatever) 2- or an internal pre-parsing phase? It should not be based on the expat library though; do we have any other possibilities among the current modules? 3- or we leave it to hand-crafting by knowledgeable people on the forum, as it is happening now? I am looking forward to opinions ... and possibily reviews of PR 122 please ;-) Best regards, -- Arrigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with duplicate attributes in XML tags
Hello Peter, All, On Thu, Feb 04, 2021 at 12:00:44PM +0100, Peter Kovacs wrote: > +1 for Option 3) > [... FTR ...] > > 3- raise an exception because it is just not acceptable. I believe it should be a subclass of uno::Exception, but... which one? There seem to be a lot of Exception's subclasses in the UNO framework. Thank you in advance, -- Arrigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with duplicate attributes in XML tags
Hello Jim, On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote: > Funny that you bring this up... I'm been tracking down some bugs and they > all seem to be XML related... :-) [...] > I feel that making AOO more fragile by trying to work around cases where > invalid and/or non-compliant XML is encountered is just wrong. We should > either ignore the error (catch it) or raise an exception. Could you please explain better what you mean by "ignore the error (catch it)"? I understand the word "catch" for exceptions... > Invalid data shouldn't be tolerated. Additionally, trying to be > "lenient" is an easy vector for vulnerabilities. I agree if we speak about the XML code generated by AOO, I mean during the export of XML data. If the save operation fails, an exception should be thrown and the user should be warned, so they can retry saving in another format, or doing copy & paste into another document... I am sure they would rather try many times than just silently risk to lose their data. Once the data is on disk, being able to recover a corrupt file would be IMHO very useful, because users get very upset if their data is suddenly lost because of a bug, and honestly, so would I. As long as errors consist of a missing end tag or a duplicated attribute, I believe we should be able to handle them with little implications for security (for what I can imagine -- I am not a security expert). In a previous thread on this ML "High priority issues", Peter pointed out this bug too: https://bz.apache.org/ooo/show_bug.cgi?id=126927 that can be generalized as "warn the user if there are problems in the input". I would like very much to have such a system in place, for example with ``warnings'' recorded during the XML parsing, and eventually displayed. Users would become worried about the unexpected warning messages emitted during load and save operations, and would come back to us (on user forums, mailing lists, BugZilla etc); this could help them (and us) better address issues, maybe even identify problems before they cause data loss. If you really do not like the "lenient" parsing, we could try to make it an optional second attempt. If the "strict" parsing fails, then the user could be offered to retry with the lenient algorithm, but being warned about possible security implications. I hope I could explain myself clearly. I believe that these topics may have already been discussed in the past; if you want to avoid discussing any already consolidated decisions, please send me the pointers. Best regards, -- Arrigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with duplicate attributes in XML tags
+1 for Option 3) On 03.02.21 19:38, Arrigo Marchiori wrote: Dear List, bug 128356 [1] is mostly about an XML tag that carries an attribute _twice_. This is not allowed; the SAX parser raises an exception when it finds it while loading the file, and the user gets upset because they cannot open their file any more. While I am looking for the actual cause of this bug, I think it may be useful to stop this XML error from happening anywhere. Our API should complain heavily when requested to do such an illegal action. I am going to add a ``safety-check'' into the methods of class SvXMLAttributeList to avoid ``adding'' an attribute that is already in the list. But what shall these methods do instead, apart from complaining? 1- just ignore the request, leaving the current value for the attribute; 2- set the new value, overwriting the current one; 3- raise an exception because it is just not acceptable. I personally like option 3-, but someone may have a different opinion? In addition to this, when finished with the bug, I will try to make the SAX parser accept these duplicated attributes, and try to carry on loading the file. This should help our angry users recover their data, even if some information may be lost. Please share your opinion. References: 1: https://bz.apache.org/ooo/show_bug.cgi?id=128356 Best regards, -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with duplicate attributes in XML tags
Funny that you bring this up... I'm been tracking down some bugs and they all seem to be XML related... fastsax->libwriterfilter with occasional cores due to __cxa_call_unexpected. I feel that making AOO more fragile by trying to work around cases where invalid and/or non-compliant XML is encountered is just wrong. We should either ignore the error (catch it) or raise an exception. Invalid data shouldn't be tolerated. Additionally, trying to be "lenient" is an easy vector for vulnerabilities. My 2c > On Feb 3, 2021, at 1:38 PM, Arrigo Marchiori wrote: > > Dear List, > > bug 128356 [1] is mostly about an XML tag that carries an attribute > _twice_. This is not allowed; the SAX parser raises an exception when > it finds it while loading the file, and the user gets upset because > they cannot open their file any more. > > While I am looking for the actual cause of this bug, I think it may be > useful to stop this XML error from happening anywhere. Our API should > complain heavily when requested to do such an illegal action. > > I am going to add a ``safety-check'' into the methods of class > SvXMLAttributeList to avoid ``adding'' an attribute that is already in > the list. But what shall these methods do instead, apart from > complaining? > > 1- just ignore the request, leaving the current value for the >attribute; > > 2- set the new value, overwriting the current one; > > 3- raise an exception because it is just not acceptable. > > I personally like option 3-, but someone may have a different opinion? > > In addition to this, when finished with the bug, I will try to make > the SAX parser accept these duplicated attributes, and try to carry on > loading the file. This should help our angry users recover their data, > even if some information may be lost. > > Please share your opinion. > > References: > 1: https://bz.apache.org/ooo/show_bug.cgi?id=128356 > > Best regards, > -- > Arrigo > > http://rigo.altervista.org > > - > 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
How to cope with duplicate attributes in XML tags
Dear List, bug 128356 [1] is mostly about an XML tag that carries an attribute _twice_. This is not allowed; the SAX parser raises an exception when it finds it while loading the file, and the user gets upset because they cannot open their file any more. While I am looking for the actual cause of this bug, I think it may be useful to stop this XML error from happening anywhere. Our API should complain heavily when requested to do such an illegal action. I am going to add a ``safety-check'' into the methods of class SvXMLAttributeList to avoid ``adding'' an attribute that is already in the list. But what shall these methods do instead, apart from complaining? 1- just ignore the request, leaving the current value for the attribute; 2- set the new value, overwriting the current one; 3- raise an exception because it is just not acceptable. I personally like option 3-, but someone may have a different opinion? In addition to this, when finished with the bug, I will try to make the SAX parser accept these duplicated attributes, and try to carry on loading the file. This should help our angry users recover their data, even if some information may be lost. Please share your opinion. References: 1: https://bz.apache.org/ooo/show_bug.cgi?id=128356 Best regards, -- Arrigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [REVIEW] How to display the platform hint text for Windows, Linux and macOS?
> -Original Message- > From: Marcus [mailto:marcus.m...@wtnet.de] > Sent: Sunday, January 10, 2021 7:48 PM > To: dev@ > Subject: [REVIEW] How to display the platform hint text for > Windows, Linux and macOS? > > As discussed, I've tried to move the platform hint text from the side > into a separate button below the both download buttons: > > https://openoffice-org.staged.apache.org/download/index.html > > The color for border and text is different to the download > buttons. For > the sure the combination is not perfect, but just to show that a > difference makes sense. +1 I think this will catch the eyes and help some users. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[REVIEW] How to display the platform hint text for Windows, Linux and macOS?
As discussed, I've tried to move the platform hint text from the side into a separate button below the both download buttons: https://openoffice-org.staged.apache.org/download/index.html The color for border and text is different to the download buttons. For the sure the combination is not perfect, but just to show that a difference makes sense. PS: At the moment the text is missing for macOS. But this is discussed in a different mail thread. Thanks for your feedback. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
Ok El dom., 3 de enero de 2021 5:27 p. m., Patricia Shanahan escribió: > > > > On Dec 27, 2020, at 10:30, Dave Fisher wrote: > > > > > > > >>> On Dec 27, 2020, at 5:13 AM, Patricia Shanahan wrote: > >>> > >>> > >>>> On Dec 27, 2020, at 04:39, Jörg Schmidt > wrote: > >>> > >>> > >>>> > >>>> -Original Message- > >>>> From: Peter Kovacs [mailto:pe...@apache.org] > >>>> Sent: Sunday, December 27, 2020 12:50 PM > >>>> To: dev@openoffice.apache.org > >>>> Subject: Re: [lazy consensus] Addition in release notes > >>>> because of Big Sur (was: How should we proceed with BigSur?) > >>>> > >>>> How about we make a blog post instead? > >>>> > >>>> We can describe > >>>> > >>>> What the impact is. > >>>> > >>>> What Versions are affected. > >>>> > >>>> Where our research is. > >>>> > >>>> And what our plans are. > >>> > >>> you mean in: https://blogs.apache.org? If so, I would find that even > better. > >>> > >>> But who can do that? I myself do not feel able to do it because: > >>> -my english is too bad for longer text > >> > >> If you do know the content for longer writing I may be able to help > with editing. I am a native speaker of the English dialect of English and > have near native reading, writing, and listening skills in the US dialect, > which I would use for an AOO blog. > > > > The proposed text is now in Confluence. (Thanks Jörg!) I’ve made many > edits. > > > > Here it is: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814 > < > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814 > > > > It looks good to me for grammar and spelling. > > > > > Regards, > > Dave > > > >> > >> > >>> -I hardly know anything about technical backgrounds > >>> > >>> If I suggested an entry in the release notes it was because: > >>> -I think it is valuable for the users to get an info as soon as > possible > >>> -I feel able to formulate a short English text for the Release Notes > >>> > >>> > >>> I thus gladly support your suggestion of a blog post. > >>> > >>> If there is nothing clear in the next few hours I will, however, after > the deadline of my proposal, state that "lazy consensus" has failed (in my > opinion) and I will reintroduce the same proposal by way of formal > "consensus building". > >>> > >>> > >>> > >>> greetings, > >>> Jörg > >>> > >>> > >>> > >>> - > >>> 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 > >> > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> On Dec 27, 2020, at 10:30, Dave Fisher wrote: > > > >>> On Dec 27, 2020, at 5:13 AM, Patricia Shanahan wrote: >>> >>> >>>> On Dec 27, 2020, at 04:39, Jörg Schmidt wrote: >>> >>> >>>> >>>> -Original Message- >>>> From: Peter Kovacs [mailto:pe...@apache.org] >>>> Sent: Sunday, December 27, 2020 12:50 PM >>>> To: dev@openoffice.apache.org >>>> Subject: Re: [lazy consensus] Addition in release notes >>>> because of Big Sur (was: How should we proceed with BigSur?) >>>> >>>> How about we make a blog post instead? >>>> >>>> We can describe >>>> >>>> What the impact is. >>>> >>>> What Versions are affected. >>>> >>>> Where our research is. >>>> >>>> And what our plans are. >>> >>> you mean in: https://blogs.apache.org? If so, I would find that even better. >>> >>> But who can do that? I myself do not feel able to do it because: >>> -my english is too bad for longer text >> >> If you do know the content for longer writing I may be able to help with >> editing. I am a native speaker of the English dialect of English and have >> near native reading, writing, and listening skills in the US dialect, which >> I would use for an AOO blog. > > The proposed text is now in Confluence. (Thanks Jörg!) I’ve made many edits. > > Here it is: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814 > <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814> It looks good to me for grammar and spelling. > > Regards, > Dave > >> >> >>> -I hardly know anything about technical backgrounds >>> >>> If I suggested an entry in the release notes it was because: >>> -I think it is valuable for the users to get an info as soon as possible >>> -I feel able to formulate a short English text for the Release Notes >>> >>> >>> I thus gladly support your suggestion of a blog post. >>> >>> If there is nothing clear in the next few hours I will, however, after the >>> deadline of my proposal, state that "lazy consensus" has failed (in my >>> opinion) and I will reintroduce the same proposal by way of formal >>> "consensus building". >>> >>> >>> >>> greetings, >>> Jörg >>> >>> >>> >>> - >>> 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 >> > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
Am 27.12.20 um 19:30 schrieb Dave Fisher: On Dec 27, 2020, at 5:13 AM, Patricia Shanahan wrote: On Dec 27, 2020, at 04:39, Jörg Schmidt wrote: -Original Message- From: Peter Kovacs [mailto:pe...@apache.org] Sent: Sunday, December 27, 2020 12:50 PM To: dev@openoffice.apache.org Subject: Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?) How about we make a blog post instead? We can describe What the impact is. What Versions are affected. Where our research is. And what our plans are. you mean in: https://blogs.apache.org? If so, I would find that even better. But who can do that? I myself do not feel able to do it because: -my english is too bad for longer text If you do know the content for longer writing I may be able to help with editing. I am a native speaker of the English dialect of English and have near native reading, writing, and listening skills in the US dialect, which I would use for an AOO blog. The proposed text is now in Confluence. (Thanks Jörg!) I’ve made many edits. Here it is: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814 <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814> I've also made some changes. @Patricia: It would be great when you can have an eye on the wording and formulations before we put this on the blog. Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> On Dec 27, 2020, at 5:13 AM, Patricia Shanahan wrote: > > >> On Dec 27, 2020, at 04:39, Jörg Schmidt wrote: >> >> >>> >>> -Original Message- >>> From: Peter Kovacs [mailto:pe...@apache.org] >>> Sent: Sunday, December 27, 2020 12:50 PM >>> To: dev@openoffice.apache.org >>> Subject: Re: [lazy consensus] Addition in release notes >>> because of Big Sur (was: How should we proceed with BigSur?) >>> >>> How about we make a blog post instead? >>> >>> We can describe >>> >>> What the impact is. >>> >>> What Versions are affected. >>> >>> Where our research is. >>> >>> And what our plans are. >> >> you mean in: https://blogs.apache.org? If so, I would find that even better. >> >> But who can do that? I myself do not feel able to do it because: >> -my english is too bad for longer text > > If you do know the content for longer writing I may be able to help with > editing. I am a native speaker of the English dialect of English and have > near native reading, writing, and listening skills in the US dialect, which I > would use for an AOO blog. The proposed text is now in Confluence. (Thanks Jörg!) I’ve made many edits. Here it is: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814 <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814> Regards, Dave > > >> -I hardly know anything about technical backgrounds >> >> If I suggested an entry in the release notes it was because: >> -I think it is valuable for the users to get an info as soon as possible >> -I feel able to formulate a short English text for the Release Notes >> >> >> I thus gladly support your suggestion of a blog post. >> >> If there is nothing clear in the next few hours I will, however, after the >> deadline of my proposal, state that "lazy consensus" has failed (in my >> opinion) and I will reintroduce the same proposal by way of formal >> "consensus building". >> >> >> >> greetings, >> Jörg >> >> >> >> - >> 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: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> -Original Message- > From: dave [mailto:b...@apache.org] > Sent: Sunday, December 27, 2020 5:28 PM > To: dev@openoffice.apache.org > Subject: Re: [lazy consensus] Addition in release notes > because of Big Sur (was: How should we proceed with BigSur?) > > On 27/12/2020 14:38, Jörg Schmidt wrote: > >> -Original Message- > >> From: Patricia Shanahan [mailto:p...@acm.org] > >> Sent: Sunday, December 27, 2020 2:13 PM > >> To: dev@openoffice.apache.org > >> Subject: Re: [lazy consensus] Addition in release notes > >> because of Big Sur (was: How should we proceed with BigSur?) > >> > >> > >>> On Dec 27, 2020, at 04:39, Jörg Schmidt > >> wrote: > > > >>> But who can do that? I myself do not feel able to do it because: > >>> -my english is too bad for longer text > >> > >> If you do know the content for longer writing I may be able > >> to help with editing. I am a native speaker of the English > >> dialect of English and have near native reading, writing, and > >> listening skills in the US dialect, which I would use for > an AOO blog. > > > > Thanks, but I think Peter's draft text is better than what > I could provide. > > Why would you reject the assistance of a native English speaking, > active, Apache OpenOffice PMC member's offer of assistance? That does > not make any sense. The reason is very simple: I myself have much less technical knowledge about the problem 'AOO/MacOS' than Peter and would have to gather the facts first. Peter's text, however, already contains the right facts (I assume) and I see no reason to make an alternative text proposal. However, I can translate Peter's text into German if it would be of interest to have an additional German text for publication. > Precisely. This and accurate English grammar is where Patricia's > contribution would be extremely valuable. I assume that Patricia's suggestion also applies to Peter's text. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
On 27/12/2020 14:38, Jörg Schmidt wrote: >> -Original Message- >> From: Patricia Shanahan [mailto:p...@acm.org] >> Sent: Sunday, December 27, 2020 2:13 PM >> To: dev@openoffice.apache.org >> Subject: Re: [lazy consensus] Addition in release notes >> because of Big Sur (was: How should we proceed with BigSur?) >> >> >>> On Dec 27, 2020, at 04:39, Jörg Schmidt >> wrote: > >>> But who can do that? I myself do not feel able to do it because: >>> -my english is too bad for longer text >> >> If you do know the content for longer writing I may be able >> to help with editing. I am a native speaker of the English >> dialect of English and have near native reading, writing, and >> listening skills in the US dialect, which I would use for an AOO blog. > > Thanks, but I think Peter's draft text is better than what I could provide. Why would you reject the assistance of a native English speaking, active, Apache OpenOffice PMC member's offer of assistance? That does not make any sense. > (whether Peter's text is spelling correct I can't say) Precisely. This and accurate English grammar is where Patricia's contribution would be extremely valuable. > greetings, > Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Sunday, December 27, 2020 2:13 PM > To: dev@openoffice.apache.org > Subject: Re: [lazy consensus] Addition in release notes > because of Big Sur (was: How should we proceed with BigSur?) > > > > On Dec 27, 2020, at 04:39, Jörg Schmidt > wrote: > > But who can do that? I myself do not feel able to do it because: > > -my english is too bad for longer text > > If you do know the content for longer writing I may be able > to help with editing. I am a native speaker of the English > dialect of English and have near native reading, writing, and > listening skills in the US dialect, which I would use for an AOO blog. Thanks, but I think Peter's draft text is better than what I could provide. (whether Peter's text is spelling correct I can't say) greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> On Dec 27, 2020, at 04:39, Jörg Schmidt wrote: > > >> >> -Original Message- >> From: Peter Kovacs [mailto:pe...@apache.org] >> Sent: Sunday, December 27, 2020 12:50 PM >> To: dev@openoffice.apache.org >> Subject: Re: [lazy consensus] Addition in release notes >> because of Big Sur (was: How should we proceed with BigSur?) >> >> How about we make a blog post instead? >> >> We can describe >> >> What the impact is. >> >> What Versions are affected. >> >> Where our research is. >> >> And what our plans are. > > you mean in: https://blogs.apache.org? If so, I would find that even better. > > But who can do that? I myself do not feel able to do it because: > -my english is too bad for longer text If you do know the content for longer writing I may be able to help with editing. I am a native speaker of the English dialect of English and have near native reading, writing, and listening skills in the US dialect, which I would use for an AOO blog. > -I hardly know anything about technical backgrounds > > If I suggested an entry in the release notes it was because: > -I think it is valuable for the users to get an info as soon as possible > -I feel able to formulate a short English text for the Release Notes > > > I thus gladly support your suggestion of a blog post. > > If there is nothing clear in the next few hours I will, however, after the > deadline of my proposal, state that "lazy consensus" has failed (in my > opinion) and I will reintroduce the same proposal by way of formal "consensus > building". > > > > greetings, > Jörg > > > > - > 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: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> -Original Message- > From: Peter Kovacs [mailto:pe...@apache.org] > Sent: Sunday, December 27, 2020 12:50 PM > To: dev@openoffice.apache.org > Subject: Re: [lazy consensus] Addition in release notes > because of Big Sur (was: How should we proceed with BigSur?) > > How about we make a blog post instead? > > We can describe > > What the impact is. > > What Versions are affected. > > Where our research is. > > And what our plans are. you mean in: https://blogs.apache.org? If so, I would find that even better. But who can do that? I myself do not feel able to do it because: -my english is too bad for longer texts -I hardly know anything about technical backgrounds If I suggested an entry in the release notes it was because: -I think it is valuable for the users to get an info as soon as possible -I feel able to formulate a short English text for the Release Notes I thus gladly support your suggestion of a blog post. If there is nothing clear in the next few hours I will, however, after the deadline of my proposal, state that "lazy consensus" has failed (in my opinion) and I will reintroduce the same proposal by way of formal "consensus building". greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
How about we make a blog post instead? We can describe What the impact is. What Versions are affected. Where our research is. And what our plans are. On 25.12.20 16:52, Jörg Schmidt wrote: -Original Message- From: Dave Fisher [mailto:wave4d...@comcast.net] Sent: Friday, December 25, 2020 4:41 PM To: dev@openoffice.apache.org Cc: ooofo...@free.fr Subject: Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?) We became aware of the problem with the release of BigSur. That just happened about the same time as the 4.1.8 release. yes. However, I am afraid (see my other mail) at the moment it is necessary to find a modified wording for the addition to the release notes, which "Bidouille" also agrees with. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
> -Original Message- > From: Jörg Schmidt [mailto:joe...@j-m-schmidt.de] > Sent: Saturday, December 26, 2020 10:05 PM > To: dev@openoffice.apache.org > Subject: RE: How should we proceed with BigSur? (was: Does > AOO 4.1.8 run under macOS Big Sur?) > > > -Original Message- > > From: Jim Jagielski [mailto:j...@jagunet.com] > > Sent: Saturday, December 26, 2020 3:18 PM > > To: dev > > Subject: Re: How should we proceed with BigSur? (was: Does > > AOO 4.1.8 run under macOS Big Sur?) > > > > It is more than likely that we may need to release a 4.1.9 > > just to accommodate BigSur. However, AOO > > is hardly unique in being an app that no longer works when > > someone upgrades to BigSur. The macOS > > community is replete w/ such apps. I'm not using that as an > > excuse, but that is what it is. > > I have not claimed anything to the contrary. > > Other "apps" are not our job, but our job is to do a good job > for AOO and currently informing the users would be part of > the good job. Oh, sorry, I thought your reply was referring to the other thread (="Addition in release notes because of Big Sur"). Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
> -Original Message- > From: Jim Jagielski [mailto:j...@jagunet.com] > Sent: Saturday, December 26, 2020 3:18 PM > To: dev > Subject: Re: How should we proceed with BigSur? (was: Does > AOO 4.1.8 run under macOS Big Sur?) > > It is more than likely that we may need to release a 4.1.9 > just to accommodate BigSur. However, AOO > is hardly unique in being an app that no longer works when > someone upgrades to BigSur. The macOS > community is replete w/ such apps. I'm not using that as an > excuse, but that is what it is. I have not claimed anything to the contrary. Other "apps" are not our job, but our job is to do a good job for AOO and currently informing the users would be part of the good job. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
For me, the issue is whether it is, indeed, a code problem in 4.1.8 that requires fixes and thus a 4.1.9 release, or whether it is a *build* problem, that implies that building 4.1.8 with a newer SDK will resolve the problem. AFAICT, that question is still unresolved. What we DO know is that 4.2.0-dev works fine under Big Sur. With that in mind, over the next week I may try building 4.1.8 but with various versions of Xcode and macOS SDKs... > On Dec 26, 2020, at 10:05 AM, Matthias Seidel > wrote: > > Hi Jim, > > Am 26.12.20 um 15:17 schrieb Jim Jagielski: >> It is more than likely that we may need to release a 4.1.9 just to >> accommodate BigSur. However, AOO >> is hardly unique in being an app that no longer works when someone upgrades >> to BigSur. The macOS >> community is replete w/ such apps. I'm not using that as an excuse, but that >> is what it is. > > More than once Apple did break something with an OS upgrade and fixed it > with one of the next updates... > > Let's see how macOS 11.2 (beta) behaves [1]. > > Regards, > >Matthias > > [1] > https://www.macrumors.com/2020/12/17/apple-seeds-macos-big-sur-11-2-public-beta-1/ > >> >> >>> On Dec 25, 2020, at 5:02 AM, Jörg Schmidt wrote: >>> >>> Hello, >>> >>> I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it >>> was also diligently discussed there. >>> But there seems to be no solution yet and at the same time the requests >>> from users who are practically not able to work anymore because AOO does >>> not work under BigSur continue. >>> >>> 1. >>> Is there any solution in sight? >>> >>> 2. >>> If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 >>> (BigSur) is currently not supported? >>> (This would give users the chance to wait with the update of MacOS to >>> version 11.0). >>> >>> >>> Sorry, my point of view is only that of a supporter who supports users day >>> by day (voluntarily in the community and professionally), I can't assess >>> the technical problems, but unfortunately I see that the current situation >>> is damaging our reputation. >>> >>> >>> >>> greetings, >>> Jörg >>> >>> >>> - >>> 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 >> > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
Hi Jim, Am 26.12.20 um 15:17 schrieb Jim Jagielski: > It is more than likely that we may need to release a 4.1.9 just to > accommodate BigSur. However, AOO > is hardly unique in being an app that no longer works when someone upgrades > to BigSur. The macOS > community is replete w/ such apps. I'm not using that as an excuse, but that > is what it is. More than once Apple did break something with an OS upgrade and fixed it with one of the next updates... Let's see how macOS 11.2 (beta) behaves [1]. Regards, Matthias [1] https://www.macrumors.com/2020/12/17/apple-seeds-macos-big-sur-11-2-public-beta-1/ > > >> On Dec 25, 2020, at 5:02 AM, Jörg Schmidt wrote: >> >> Hello, >> >> I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it was >> also diligently discussed there. >> But there seems to be no solution yet and at the same time the requests from >> users who are practically not able to work anymore because AOO does not work >> under BigSur continue. >> >> 1. >> Is there any solution in sight? >> >> 2. >> If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 >> (BigSur) is currently not supported? >> (This would give users the chance to wait with the update of MacOS to >> version 11.0). >> >> >> Sorry, my point of view is only that of a supporter who supports users day >> by day (voluntarily in the community and professionally), I can't assess >> the technical problems, but unfortunately I see that the current situation >> is damaging our reputation. >> >> >> >> greetings, >> Jörg >> >> >> - >> 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 > smime.p7s Description: S/MIME Cryptographic Signature
Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
It is more than likely that we may need to release a 4.1.9 just to accommodate BigSur. However, AOO is hardly unique in being an app that no longer works when someone upgrades to BigSur. The macOS community is replete w/ such apps. I'm not using that as an excuse, but that is what it is. > On Dec 25, 2020, at 5:02 AM, Jörg Schmidt wrote: > > Hello, > > I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it was > also diligently discussed there. > But there seems to be no solution yet and at the same time the requests from > users who are practically not able to work anymore because AOO does not work > under BigSur continue. > > 1. > Is there any solution in sight? > > 2. > If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 > (BigSur) is currently not supported? > (This would give users the chance to wait with the update of MacOS to version > 11.0). > > > Sorry, my point of view is only that of a supporter who supports users day by > day (voluntarily in the community and professionally), I can't assess the > technical problems, but unfortunately I see that the current situation is > damaging our reputation. > > > > greetings, > Jörg > > > - > 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: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> -Original Message- > From: Dave Fisher [mailto:wave4d...@comcast.net] > Sent: Friday, December 25, 2020 4:41 PM > To: dev@openoffice.apache.org > Cc: ooofo...@free.fr > Subject: Re: [lazy consensus] Addition in release notes > because of Big Sur (was: How should we proceed with BigSur?) > > We became aware of the problem with the release of BigSur. > That just happened about the same time as the 4.1.8 release. yes. However, I am afraid (see my other mail) at the moment it is necessary to find a modified wording for the addition to the release notes, which "Bidouille" also agrees with. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> -Original Message- > From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] > Sent: Friday, December 25, 2020 3:51 PM > To: dev@openoffice.apache.org > Subject: Re: [lazy consensus] Addition in release notes > because of Big Sur (was: How should we proceed with BigSur?) > > Am 25.12.20 um 15:44 schrieb Bidouille: > >> Unfortunately these problems became apparent after the > >> release of AOO 4.1.8 > > I disagree. > > Some users have reported this bug with old builds (4.1.3 > and 4.1.7 too). > > And how does that contradict above sentence?! imho: I am afraid that with the method "lazy consensus" everyone can object without having to give a reason, and I am afraid that if the objection is upheld then "lazy consensus" has failed and we must have to take a formal vote. In any case, in the rules of "lazy consensus" there is no other way to neutralize the opposition, because the possibility of counterproposals is purely voluntary and not mandatory: https://community.apache.org/committers/lazyConsensus.html Any other opinions? Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
We became aware of the problem with the release of BigSur. That just happened about the same time as the 4.1.8 release. 4.1.9 is another discussion. Regards, Dave Sent from my iPhone > On Dec 25, 2020, at 7:24 AM, Jörg Schmidt wrote: > > >> >> -Original Message- >> From: Bidouille [mailto:ooofo...@free.fr] >> Sent: Friday, December 25, 2020 3:45 PM >> To: dev@openoffice.apache.org >> Subject: Re: [lazy consensus] Addition in release notes >> because of Big Sur (was: How should we proceed with BigSur?) >> >>> Unfortunately these problems became apparent after the >>> release of AOO 4.1.8 >> I disagree. >> Some users have reported this bug with old builds (4.1.3 and >> 4.1.7 too). > > maybe i could write: > > Although there were already hints with earlier program versions, it was only > with AOO 4.1.8 that we became aware of the problem, unfortunately only after > the release, due to an increased number of feedbacks - a solution to the > problem is already being worked on. > > > Better? > > > Jörg > > > > > - > 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: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> -Original Message- > From: Bidouille [mailto:ooofo...@free.fr] > Sent: Friday, December 25, 2020 3:45 PM > To: dev@openoffice.apache.org > Subject: Re: [lazy consensus] Addition in release notes > because of Big Sur (was: How should we proceed with BigSur?) > > > Unfortunately these problems became apparent after the > > release of AOO 4.1.8 > I disagree. > Some users have reported this bug with old builds (4.1.3 and > 4.1.7 too). maybe i could write: Although there were already hints with earlier program versions, it was only with AOO 4.1.8 that we became aware of the problem, unfortunately only after the release, due to an increased number of feedbacks - a solution to the problem is already being worked on. Better? Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
Am 25.12.20 um 15:44 schrieb Bidouille: >> Unfortunately these problems became apparent after the >> release of AOO 4.1.8 > I disagree. > Some users have reported this bug with old builds (4.1.3 and 4.1.7 too). And how does that contradict above sentence?! > > - > 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
Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> Unfortunately these problems became apparent after the > release of AOO 4.1.8 I disagree. Some users have reported this bug with old builds (4.1.3 and 4.1.7 too). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)
> However, we really should state this (known) Problem > in our Release Notes. Hello, If there is no objection I will add the following to the release notes for AOO 4.1.8, starting 12/28/2020 at 5:00 PM (CET): In the release notes under "Known Issues - For macOS users": (en) Note for MacOS 11.0.x, Big Sur AOO 4.1.8 is not able to open OOXML files (docx, xlsx, ...) under MacOS 11.0.x. Unfortunately these problems became apparent after the release of AOO 4.1.8, a solution is already being worked on. (de) Hinweis für MacOS 11.0.x, Big Sur AOO 4.1.8 ist unter MacOS 11.0.x nicht in der Lage OOXML-Dateien (docx, xlsx, ...) zu öffnen. Leider haben sich diese Probleme erst nach dem Release von AOO 4.1.8 herausgestellt, an einer Problemlösung wird bereits gearbeitet. I will only add the following (additionally) if there are positive comments about it here in the thread: (en) As a workaround, it is recommended to refrain from updating MacOS to version 11.0.x for the time being and to keep an earlier version. (de) Als workaround wird empfohlen vorerst auf das Update von MacOS auf Version 11.0.x zu verzichten und eine frühere Version beizubehalten. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
Hi Mechtilde, Am 25.12.20 um 12:51 schrieb Mechtilde: > Hello Jörg, > > Am 25.12.20 um 12:22 schrieb Jörg Schmidt: >> Hello Mechtilde, >> >>> -Original Message- >>> From: Mechtilde [mailto:o...@mechtilde.de] >>> Sent: Friday, December 25, 2020 11:28 AM >>> To: dev@openoffice.apache.org >>> Subject: Re: How should we proceed with BigSur? (was: Does >>> AOO 4.1.8 run under macOS Big Sur?) >>> >>> Hello jörg, >>> >>> here is the last test to fix this problem. >>> >>> http://home.apache.org/~jim/AOO-builds/ >>> >>> this build is from yesterday. >> 1. >> May I share this link elsewhere (e.g. in http://de.openoffice.info)? >> >> 2. >> I don't know if there are plans to replace the official download version >> with this new version and how fast that would be. >> Would it be a way to list this version, with appropriate notes (which we >> should discuss briefly) in the release notes. >> > First we need feedback from tester whether this build works as expected. I can confirm that this build can open docx. But this is a different branch and I am not sure if it ever was affected by the problem. @Jim: Checking for updates is functional again for me! However, we really should state this (known) Problem in our Release Notes. Regards, Matthias > > Regards > smime.p7s Description: S/MIME Cryptographic Signature
Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
Hello Jörg, Am 25.12.20 um 12:22 schrieb Jörg Schmidt: > Hello Mechtilde, > >> -Original Message- >> From: Mechtilde [mailto:o...@mechtilde.de] >> Sent: Friday, December 25, 2020 11:28 AM >> To: dev@openoffice.apache.org >> Subject: Re: How should we proceed with BigSur? (was: Does >> AOO 4.1.8 run under macOS Big Sur?) >> >> Hello jörg, >> >> here is the last test to fix this problem. >> >> http://home.apache.org/~jim/AOO-builds/ >> >> this build is from yesterday. > > 1. > May I share this link elsewhere (e.g. in http://de.openoffice.info)? > > 2. > I don't know if there are plans to replace the official download version with > this new version and how fast that would be. > Would it be a way to list this version, with appropriate notes (which we > should discuss briefly) in the release notes. > First we need feedback from tester whether this build works as expected. Regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
RE: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
> -Original Message- > From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] > Sent: Friday, December 25, 2020 11:56 AM > To: dev@openoffice.apache.org > Subject: Re: How should we proceed with BigSur? (was: Does > AOO 4.1.8 run under macOS Big Sur?) > > Hi Mechtilde, > > Am 25.12.20 um 11:27 schrieb Mechtilde: > > Hello jörg, > > > > here is the last test to fix this problem. > > > > http://home.apache.org/~jim/AOO-builds/ > > > > this build is from yesterday. > > Yes, but that is a branch we will not be releasing soon... ;-) > > AOO 4.1.8 *does* run on Big Sur, but we have an open issue > with opening > docx files. > This and some other "glitches" would (IMHO) justify a new 4.1.9 build. +1 I can only emphasize again the situation for the normal macOS users is currently very unpleasant, they update to BigSur and then AOO no longer runs properly. (The end-users do not distinguish between general problems and problems with file types.) If there is no new Release there must be an info(*) in the release notes. as soon as possible. (*) I can do the work of writing, however, the decision to publish such a info/notice we must make together. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
Hello Mechtilde, > -Original Message- > From: Mechtilde [mailto:o...@mechtilde.de] > Sent: Friday, December 25, 2020 11:28 AM > To: dev@openoffice.apache.org > Subject: Re: How should we proceed with BigSur? (was: Does > AOO 4.1.8 run under macOS Big Sur?) > > Hello jörg, > > here is the last test to fix this problem. > > http://home.apache.org/~jim/AOO-builds/ > > this build is from yesterday. Thank you. May I share this link with an end-user at users...@openoffice.apache.org? furthermore: 1. May I share this link elsewhere (e.g. in http://de.openoffice.info)? 2. I don't know if there are plans to replace the official download version with this new version and how fast that would be. Would it be a way to list this version, with appropriate notes (which we should discuss briefly) in the release notes. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
Hi Mechtilde, Am 25.12.20 um 11:27 schrieb Mechtilde: > Hello jörg, > > here is the last test to fix this problem. > > http://home.apache.org/~jim/AOO-builds/ > > this build is from yesterday. Yes, but that is a branch we will not be releasing soon... ;-) AOO 4.1.8 *does* run on Big Sur, but we have an open issue with opening docx files. This and some other "glitches" would (IMHO) justify a new 4.1.9 build. BTW: Have some nice days for Christmas! We are all spending so much of our private time on this project, it should never be forgotten that we all deserve some private time. Especially after this "special" year. Looking forward to 2021! Regards, Matthias > Regards > > Mechtilde > > Am 25.12.20 um 11:02 schrieb Jörg Schmidt: >> Hello, >> >> I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it was >> also diligently discussed there. >> But there seems to be no solution yet and at the same time the requests from >> users who are practically not able to work anymore because AOO does not work >> under BigSur continue. >> >> 1. >> Is there any solution in sight? >> >> 2. >> If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 >> (BigSur) is currently not supported? >> (This would give users the chance to wait with the update of MacOS to >> version 11.0). >> >> >> Sorry, my point of view is only that of a supporter who supports users day >> by day (voluntarily in the community and professionally), I can't assess >> the technical problems, but unfortunately I see that the current situation >> is damaging our reputation. >> >> >> >> greetings, >> Jörg >> >> >> - >> 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
Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
Hello jörg, here is the last test to fix this problem. http://home.apache.org/~jim/AOO-builds/ this build is from yesterday. Regards Mechtilde Am 25.12.20 um 11:02 schrieb Jörg Schmidt: > Hello, > > I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it was > also diligently discussed there. > But there seems to be no solution yet and at the same time the requests from > users who are practically not able to work anymore because AOO does not work > under BigSur continue. > > 1. > Is there any solution in sight? > > 2. > If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 > (BigSur) is currently not supported? > (This would give users the chance to wait with the update of MacOS to version > 11.0). > > > Sorry, my point of view is only that of a supporter who supports users day by > day (voluntarily in the community and professionally), I can't assess the > technical problems, but unfortunately I see that the current situation is > damaging our reputation. > > > > greetings, > Jörg > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)
Hello, I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it was also diligently discussed there. But there seems to be no solution yet and at the same time the requests from users who are practically not able to work anymore because AOO does not work under BigSur continue. 1. Is there any solution in sight? 2. If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 (BigSur) is currently not supported? (This would give users the chance to wait with the update of MacOS to version 11.0). Sorry, my point of view is only that of a supporter who supports users day by day (voluntarily in the community and professionally), I can't assess the technical problems, but unfortunately I see that the current situation is damaging our reputation. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with Python module putting .so files into lib64 instead of lib?
I think we can only try to build and install on many distributions. If it is only a folder change I think it should be save. At least Arch /usr/lib is only a softlink to /usr/lib64 On 07.12.20 08:30, Arrigo Marchiori wrote: Dear List, I think I am close to a possible solution to this problem, that I will propose as a pull request on GitHub once it will be ready. I would like to make sure that Python and the pyuno modules are built correctly and that they work as expected in my test builds. Can someone please suggest me how to check them? Thank you in advance and best regards. On Sat, Nov 21, 2020 at 08:51:02PM +0100, Arrigo Marchiori wrote: Dear List, I am going forward in building OpenOffice on openSUSE Leap 15.2. I am encountering problems with the pyuno modules and I think they may be due to an incomplete installation of the "python" module. Just to clarify: I am not talking about my system Python, but rather the "python" module from AOO sources directory main/python. openSUSE has a long tradition of putting 64-bit libraries in /usr/lib64 and, on my system, the Python version compiled as "python" module is doing the same: $ find path/main/python/unxlngx6.pro -name libpython*.so* path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so.1.0 path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so.1.0 However, file path/main/python/prj/d.lst seem to explicitly look for files in "lib" rather than "lib64": [line 86] ..\%__SRC%\misc\build\python-inst\lib\libpython2.7.so.1.0 %_DEST%\lib%_EXT%\libpython2.7.so.1.0 ^ Can anyone please confirm that it is possible to carry out a 64-bit build on a 64-bit Linux system that keeps its 64-bit libraries in /lib64 ? Or has anyone ever addressed this kind of problem in the OpenOffice build system? Thank you in advance! -- rigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to cope with Python module putting .so files into lib64 instead of lib?
Dear List, I think I am close to a possible solution to this problem, that I will propose as a pull request on GitHub once it will be ready. I would like to make sure that Python and the pyuno modules are built correctly and that they work as expected in my test builds. Can someone please suggest me how to check them? Thank you in advance and best regards. On Sat, Nov 21, 2020 at 08:51:02PM +0100, Arrigo Marchiori wrote: > Dear List, > > I am going forward in building OpenOffice on openSUSE Leap 15.2. > > I am encountering problems with the pyuno modules and I think they may > be due to an incomplete installation of the "python" module. > > Just to clarify: I am not talking about my system Python, but rather > the "python" module from AOO sources directory main/python. > > openSUSE has a long tradition of putting 64-bit libraries in > /usr/lib64 and, on my system, the Python version compiled as "python" > module is doing the same: > > $ find path/main/python/unxlngx6.pro -name libpython*.so* > path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so > path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so.1.0 > path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so > path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so.1.0 > > However, file path/main/python/prj/d.lst seem to explicitly look for > files in "lib" rather than "lib64": > > [line 86] > ..\%__SRC%\misc\build\python-inst\lib\libpython2.7.so.1.0 > %_DEST%\lib%_EXT%\libpython2.7.so.1.0 > ^ > > Can anyone please confirm that it is possible to carry out a 64-bit > build on a 64-bit Linux system that keeps its 64-bit libraries in > /lib64 ? > > Or has anyone ever addressed this kind of problem in the OpenOffice > build system? > > Thank you in advance! > -- > rigo > > http://rigo.altervista.org -- rigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How to cope with Python module putting .so files into lib64 instead of lib?
Dear List, I am going forward in building OpenOffice on openSUSE Leap 15.2. I am encountering problems with the pyuno modules and I think they may be due to an incomplete installation of the "python" module. Just to clarify: I am not talking about my system Python, but rather the "python" module from AOO sources directory main/python. openSUSE has a long tradition of putting 64-bit libraries in /usr/lib64 and, on my system, the Python version compiled as "python" module is doing the same: $ find path/main/python/unxlngx6.pro -name libpython*.so* path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so.1.0 path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so.1.0 However, file path/main/python/prj/d.lst seem to explicitly look for files in "lib" rather than "lib64": [line 86] ..\%__SRC%\misc\build\python-inst\lib\libpython2.7.so.1.0 %_DEST%\lib%_EXT%\libpython2.7.so.1.0 ^ Can anyone please confirm that it is possible to carry out a 64-bit build on a 64-bit Linux system that keeps its 64-bit libraries in /lib64 ? Or has anyone ever addressed this kind of problem in the OpenOffice build system? Thank you in advance! -- rigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to create a child page in Apache OpenOffice Community space (cwiki)?
Hi Dave, It is working now. Thank you. And I have finally found the answer to my question: > > Am I missing something or too dumb? > The answer is YES and YES. :'‑) Regards, Czesław вт, 17 нояб. 2020 г. в 23:38, Dave Fisher : > Hi - > > This was a permissions issue. You should be good now. > > Regards, > Dave > > > On Nov 17, 2020, at 1:33 PM, Czesław Wolański < > czeslaw.wolan...@gmail.com> wrote: > > > > Hi Dave, Andrea > > > > @Dave > > I understand your words but when I start here (being logged in): > > > > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 > > > > - on the bottom of the left navigation I see only "Space tools" > > - just to the right of the breadcrumbs there is no an outline icon > > (and what is "the edit page"?) > > - I see no "Create child page" to press. > > > > @Andrea > > I have already tried the Copy function - got a message: > > "You do not have permission to add pages to the space you have selected. > > Please choose a different space" > > > > That is why I choose the "Create" button to compose a draft... > > > > Thank you both for your patience. > > > > Regards > > Czesław > > > > > > > > > > вт, 17 нояб. 2020 г. в 21:30, Dave Fisher : > > > >> If you start here: > >> > >> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 > >> > >> All you need to do is press Create child page > >> > >>> On Nov 17, 2020, at 12:26 PM, Dave Fisher wrote: > >>> > >>> Hi - > >>> > >>> Create child page on the bottom of the left navigation. > >>> > >>> On the edit page just to the right of the breadcrumbs is an outline > >> icon. Press that! > >>> > >>> Regards, > >>> Dave > >>> > >>>> On Nov 17, 2020, at 12:22 PM, Czesław Wolański < > >> czeslaw.wolan...@gmail.com> wrote: > >>>> > >>>> Hi all, > >>>> > >>>> Could someone please explain to me in layman's term how to create a > >> child > >>>> page for AOO 4.1.8 Release Notes? > >>>> > >>>> I studied online help and offline manual for Confluence, tried a few > >> times > >>>> and ended up with a draft in APACHECON / Dashboard / Home. > >>>> I can neither move it to Apache OpenOffice Community space nor create > a > >>>> blank page therein. > >>>> > >>>> Am I missing something or too dumb? > >>>> > >>>> Regards > >>>> Czesław Wolański > >>> > >>> > >>> - > >>> 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 > >> > >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: How to create a child page in Apache OpenOffice Community space (cwiki)?
Hi - This was a permissions issue. You should be good now. Regards, Dave > On Nov 17, 2020, at 1:33 PM, Czesław Wolański > wrote: > > Hi Dave, Andrea > > @Dave > I understand your words but when I start here (being logged in): > > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 > > - on the bottom of the left navigation I see only "Space tools" > - just to the right of the breadcrumbs there is no an outline icon > (and what is "the edit page"?) > - I see no "Create child page" to press. > > @Andrea > I have already tried the Copy function - got a message: > "You do not have permission to add pages to the space you have selected. > Please choose a different space" > > That is why I choose the "Create" button to compose a draft... > > Thank you both for your patience. > > Regards > Czesław > > > > > вт, 17 нояб. 2020 г. в 21:30, Dave Fisher : > >> If you start here: >> >> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 >> >> All you need to do is press Create child page >> >>> On Nov 17, 2020, at 12:26 PM, Dave Fisher wrote: >>> >>> Hi - >>> >>> Create child page on the bottom of the left navigation. >>> >>> On the edit page just to the right of the breadcrumbs is an outline >> icon. Press that! >>> >>> Regards, >>> Dave >>> >>>> On Nov 17, 2020, at 12:22 PM, Czesław Wolański < >> czeslaw.wolan...@gmail.com> wrote: >>>> >>>> Hi all, >>>> >>>> Could someone please explain to me in layman's term how to create a >> child >>>> page for AOO 4.1.8 Release Notes? >>>> >>>> I studied online help and offline manual for Confluence, tried a few >> times >>>> and ended up with a draft in APACHECON / Dashboard / Home. >>>> I can neither move it to Apache OpenOffice Community space nor create a >>>> blank page therein. >>>> >>>> Am I missing something or too dumb? >>>> >>>> Regards >>>> Czesław Wolański >>> >>> >>> - >>> 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 >> >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to create a child page in Apache OpenOffice Community space (cwiki)?
Hi Dave, Andrea @Dave I understand your words but when I start here (being logged in): https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 - on the bottom of the left navigation I see only "Space tools" - just to the right of the breadcrumbs there is no an outline icon (and what is "the edit page"?) - I see no "Create child page" to press. @Andrea I have already tried the Copy function - got a message: "You do not have permission to add pages to the space you have selected. Please choose a different space" That is why I choose the "Create" button to compose a draft... Thank you both for your patience. Regards Czesław вт, 17 нояб. 2020 г. в 21:30, Dave Fisher : > If you start here: > > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 > > All you need to do is press Create child page > > > On Nov 17, 2020, at 12:26 PM, Dave Fisher wrote: > > > > Hi - > > > > Create child page on the bottom of the left navigation. > > > > On the edit page just to the right of the breadcrumbs is an outline > icon. Press that! > > > > Regards, > > Dave > > > >> On Nov 17, 2020, at 12:22 PM, Czesław Wolański < > czeslaw.wolan...@gmail.com> wrote: > >> > >> Hi all, > >> > >> Could someone please explain to me in layman's term how to create a > child > >> page for AOO 4.1.8 Release Notes? > >> > >> I studied online help and offline manual for Confluence, tried a few > times > >> and ended up with a draft in APACHECON / Dashboard / Home. > >> I can neither move it to Apache OpenOffice Community space nor create a > >> blank page therein. > >> > >> Am I missing something or too dumb? > >> > >> Regards > >> Czesław Wolański > > > > > > - > > 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: How to create a child page in Apache OpenOffice Community space (cwiki)?
Dave Fisher wrote: If you start here: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 All you need to do is press Create child page Actually, what I usually do is to copy the page; the Copy function asks what page to use as parent and there one can specify the original page as parent. This allows in-line translation which is often faster. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to create a child page in Apache OpenOffice Community space (cwiki)?
If you start here: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.8 All you need to do is press Create child page > On Nov 17, 2020, at 12:26 PM, Dave Fisher wrote: > > Hi - > > Create child page on the bottom of the left navigation. > > On the edit page just to the right of the breadcrumbs is an outline icon. > Press that! > > Regards, > Dave > >> On Nov 17, 2020, at 12:22 PM, Czesław Wolański >> wrote: >> >> Hi all, >> >> Could someone please explain to me in layman's term how to create a child >> page for AOO 4.1.8 Release Notes? >> >> I studied online help and offline manual for Confluence, tried a few times >> and ended up with a draft in APACHECON / Dashboard / Home. >> I can neither move it to Apache OpenOffice Community space nor create a >> blank page therein. >> >> Am I missing something or too dumb? >> >> Regards >> Czesław Wolański > > > - > 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: How to create a child page in Apache OpenOffice Community space (cwiki)?
Hi - Create child page on the bottom of the left navigation. On the edit page just to the right of the breadcrumbs is an outline icon. Press that! Regards, Dave > On Nov 17, 2020, at 12:22 PM, Czesław Wolański > wrote: > > Hi all, > > Could someone please explain to me in layman's term how to create a child > page for AOO 4.1.8 Release Notes? > > I studied online help and offline manual for Confluence, tried a few times > and ended up with a draft in APACHECON / Dashboard / Home. > I can neither move it to Apache OpenOffice Community space nor create a > blank page therein. > > Am I missing something or too dumb? > > Regards > Czesław Wolański - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How to create a child page in Apache OpenOffice Community space (cwiki)?
Hi all, Could someone please explain to me in layman's term how to create a child page for AOO 4.1.8 Release Notes? I studied online help and offline manual for Confluence, tried a few times and ended up with a draft in APACHECON / Dashboard / Home. I can neither move it to Apache OpenOffice Community space nor create a blank page therein. Am I missing something or too dumb? Regards Czesław Wolański
Possible error in File https://www.openoffice.org/sc/excelfileformat.pdf (was: How to go about confirming a possible bug and contributing updates to a document )
Hello Jay, Am 21.10.20 um 16:49 schrieb Jay Wren (jawren): Hello, I hope this message finds you well. First, I want to thank you for https://www.openoffice.org/sc/excelfileformat.pdf I have found it invaluable. Thank you. You are welcome. It is good to know that people take interest in our pages. :) I wanted to ask about a possible bug or submitting a patch to this document. I think I may have found an error in the size table in section 3.4.7. Specifically, tFunc and tFuncVar on page 43. The BIFF8 size is listed at 4 and 5 respectively. However, in section 3.7.1 and 3.7.2 only 3 bytes and 4 bytes respectively are documented. Indeed in practice as I write a parser, I can only read 4 bytes and not 5 for tFuncVar. I am not sure if we have a editable Document somewhere. I switch from recruitment to dev List. Maybe someone knows if we have an better editor able file that we can provide you for a fix.. I am not sure, but our code reads 4 Tokes Int16. I do not see a fifth. So this sounds according to your observation. http://opengrok.openoffice.org/xref/trunk/main/oox/source/xls/formulaparser.cxx?r=a893be29#importFuncVarToken4 I am not sure if Apache POI has also some input on this? I am a bit unfamiliar with their Project. *Dave* you have some idea how to quickly search the POI Code? If I missed something, I’d love to be corrected. If I did not, I’d love to contribute if you suggest. Contribution are all welcome. I think it is best to create a ticket in Bugzilla, upload your patch there. And bring then the case to an attention on the dev list, by answering to this thread with the ticket. Just for better awarness. :) all the best Peter - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: how to download RC2?
Hi Don, https://dist.apache.org/repos/dist/dev/openoffice/4.1.8-RC2/source/ Regards, Matthias Am 08.10.20 um 20:34 schrieb Don Lewis: > I want to download the source tarball for RC2, but this page: > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-fullsets > isn't helpful. > > > - > 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
how to download RC2?
I want to download the source tarball for RC2, but this page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-fullsets isn't helpful. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to join Docs team
On 4/1/2020 3:14 PM, Jörg Schmidt wrote: >> -Original Message- >> From: Simon Phipps [mailto:webm...@apache.org] >> Sent: Wednesday, April 01, 2020 8:04 PM >> To: dev >> Subject: Re: How to join Docs team >> >> On Wed, Apr 1, 2020 at 5:32 PM Jörg Schmidt >> wrote: >> >>> Hello, >>> >>>> From: bmcs [mailto:b...@apache.org] >>>> Authors to ODF Authors. The idea being that it would be >> one of the few >>>> shared areas where AOO and LO could work cooperatively >>>> together >>> >>> I don't believe that at that time, after all the slander >> and lies on the >>> part of LO, against AOO, cooperation was still possible! >>> >>> It should never be forgotten how the highest representatives of our >>> project (for example Rob Weir) were publicly insulted by >> TDF members. >>> >> >> Seriously, can we let it go please? This sort of posting >> creates a hostile >> environment that discourages participation. > > Should the culprits at LO apologize to the AOO community for their actions at > that time, there will be no need for such contributions from me anymore. > > There is not a single public statement by the TDF against bashing AOO, and > bashing in forums, mailing lists etc. has only one direction in the present: > against AOO. > > > Jörg > Jorg others have said it now I will add my voice to it. Please stop these types of posts they are totally unproductive. They serve no purpose except rekindle and inflame incidents best left in the past. Let us all move on and foster cooperation were it is possible and move forward separately were it is not. Regards Keith signature.asc Description: OpenPGP digital signature
Re: How to join Docs team
I asked that. He said there is no mail. All the best Peter Am 05.04.20 um 10:19 schrieb Matthias Seidel: Hi Peter, Am 05.04.20 um 10:16 schrieb Peter Kovacs: Hi Keith, Pulkit Krishna, writes he does not find any mail with the login data. Gmail... He should look in his Spam folder. This happens so often... Regards, Matthias Can you check and send the email again? Thanks, All the Best Peter Am 29.03.20 um 18:19 schrieb Keith N. McKenna: On 3/27/2020 5:37 AM, Pulkit Krishna wrote: Hello, I want wiki account with useride:- pulkitkrishna email:- pulkitkrishn...@gmail.com Pulkit Krishna Pulkit; Your requested mwiki account has been created and a temporary password has been sent and please make sure you change it at first login. We currently do all documentation at the following link: https://wiki.openoffice.org/wiki/Documentation/UserGuide. It does not look as if the Base Section has been added yet I will add it later today. A good reference before starting and as you progress is https://wiki.openoffice.org/wiki/Documentation/Dashboard/Help_Style_Guide and https://wiki.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policy. You should also subscribe to the documentation mailing list at doc-subscr...@openoffice.apache.org. That list is dedicated to communication around documentation. Welcome to the documentation team. Regards Keith N. McKenna - 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: How to join Docs team
Hi Peter, Am 05.04.20 um 10:16 schrieb Peter Kovacs: > Hi Keith, > > Pulkit Krishna, writes he does not find any mail with the login data. Gmail... He should look in his Spam folder. This happens so often... Regards, Matthias > > Can you check and send the email again? > > > Thanks, > > > All the Best > > Peter > > Am 29.03.20 um 18:19 schrieb Keith N. McKenna: >> On 3/27/2020 5:37 AM, Pulkit Krishna wrote: >>> Hello, >>> I want wiki account with useride:- pulkitkrishna email:- >>> pulkitkrishn...@gmail.com >>> Pulkit Krishna >> Pulkit; >> >> Your requested mwiki account has been created and a temporary password >> has been sent and please make sure you change it at first login. We >> currently do all documentation at the following link: >> https://wiki.openoffice.org/wiki/Documentation/UserGuide. It does not >> look as if the Base Section has been added yet I will add it later >> today. A good reference before starting and as you progress is >> https://wiki.openoffice.org/wiki/Documentation/Dashboard/Help_Style_Guide >> and >> https://wiki.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policy. >> >> You should also subscribe to the documentation mailing list at >> doc-subscr...@openoffice.apache.org. That list is dedicated to >> communication around documentation. Welcome to the documentation team. >> >> Regards >> Keith N. McKenna >> >> > > - > 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
Re: How to join Docs team
Hi Keith, Pulkit Krishna, writes he does not find any mail with the login data. Can you check and send the email again? Thanks, All the Best Peter Am 29.03.20 um 18:19 schrieb Keith N. McKenna: On 3/27/2020 5:37 AM, Pulkit Krishna wrote: Hello, I want wiki account with useride:- pulkitkrishna email:- pulkitkrishn...@gmail.com Pulkit Krishna Pulkit; Your requested mwiki account has been created and a temporary password has been sent and please make sure you change it at first login. We currently do all documentation at the following link: https://wiki.openoffice.org/wiki/Documentation/UserGuide. It does not look as if the Base Section has been added yet I will add it later today. A good reference before starting and as you progress is https://wiki.openoffice.org/wiki/Documentation/Dashboard/Help_Style_Guide and https://wiki.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policy. You should also subscribe to the documentation mailing list at doc-subscr...@openoffice.apache.org. That list is dedicated to communication around documentation. Welcome to the documentation team. Regards Keith N. McKenna - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
Two short additions. 1) When we revise existing documentation we must take into account their licenses. If someone thinks we can (and don't) change an existing license to Apache, they can do so themselves. On the other hand, if a license change is not possible, it is not for us either. 2. please note that prooo-box.org is a separate platform, just like ODF authors, and welcome the work of both or neither of them. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
Hello, > -Original Message- > From: Dave Fisher [mailto:wave4d...@comcast.net] > Sent: Thursday, April 02, 2020 2:09 AM > To: dev@openoffice.apache.org > Subject: Re: [discussion] Documentation Contribution based or > produced by LO? (was: How to join Docs team) > I made a commit on the website that was valid, but he thought > it was a bad idea. So he reverted it instead of asking me. Well, it happened to me. Can you understand that I still think this is much less bad than the insults and lies from TDF/LO? > This was not proper. TBH I found him to be omnipresent and > while very helpful did not leave others enough room to grow > into also helpful. It was as if every fourth email was from > him. And then IBM pulled out and ... Rob slowly went away. This, however, is an interesting observation. I find it amazing that the PMC still insists on keeping these people in their ranks. Even though they are no longer doing anything for the project. Do you think that's right? My opinion is: IBM has done harm to the project by uncoordinatedly withdrawing its support. Specifically, this concerns the OOXML filters. > BTW we can now put the registered trademark (R) next to > Apache and OpenOffice. We had every right to it for > OpenOffice.org back at that time. It’s what I did. He had > incorrect fear that doing that was some type of major legal jeopardy. But why do we use these legal possibilities so little? Why, for example, do we not take legal action against fraudulent sites such as openoffice.de and dispute their rights? > > > > I don't understand what you mean. What do you think I want? > > > > I can say what I want myself: > > I want AOO (i mean the project and the community) to be > treated with respect. Respect, however, is a question of > joint discussion and not of one-sided subjugation. > > We all want that. All right, if we agree on this. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
Sent from my iPhone > On Apr 1, 2020, at 1:21 PM, Jörg Schmidt wrote: > > >> >> -Original Message- >> From: Dave Fisher [mailto:w...@apache.org] >> Sent: Wednesday, April 01, 2020 10:05 PM >> To: dev >> Subject: Re: [discussion] Documentation Contribution based or >> produced by LO? (was: How to join Docs team) > >> Rob Weir never apologized to me. There are people in this >> world who never, ever admit to any errors. >> >> I’m not one of them. >> >> Apologies. While I agree with your sentiment it will not lead >> to what you want if we keep bringing this issue up. > > What did Rob have to apologize for? I don't know anything he has to apologize > for. I made a commit on the website that was valid, but he thought it was a bad idea. So he reverted it instead of asking me. This was not proper. TBH I found him to be omnipresent and while very helpful did not leave others enough room to grow into also helpful. It was as if every fourth email was from him. And then IBM pulled out and ... Rob slowly went away. BTW we can now put the registered trademark (R) next to Apache and OpenOffice. We had every right to it for OpenOffice.org back at that time. It’s what I did. He had incorrect fear that doing that was some type of major legal jeopardy. > > I don't understand what you mean. What do you think I want? > > I can say what I want myself: > I want AOO (i mean the project and the community) to be treated with respect. > Respect, however, is a question of joint discussion and not of one-sided > subjugation. We all want that. We just disagree about how that may happen. Best, Dave > > > greetings, > Jörg > > > > > - > 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: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
Moin, In the past, the Prooo-Box was informed about the updating and revision of the German documentation. The only response was to state that it did not comply with the Apache license. If this is the main concern, one should not be surprised that motivation knows no bounds. Some more information about our work: The English documentation for version 3.3 serves as a basis. In this documentation some functions are described incorrectly or there are descriptions are missing. This means that all functionalities must be tested or reproduced for the new documentation will be. Alternative paths are also offered for faulty functions. Jan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
> -Original Message- > From: Dave Fisher [mailto:w...@apache.org] > Sent: Wednesday, April 01, 2020 10:05 PM > To: dev > Subject: Re: [discussion] Documentation Contribution based or > produced by LO? (was: How to join Docs team) > Rob Weir never apologized to me. There are people in this > world who never, ever admit to any errors. > > I’m not one of them. > > Apologies. While I agree with your sentiment it will not lead > to what you want if we keep bringing this issue up. What did Rob have to apologize for? I don't know anything he has to apologize for. I don't understand what you mean. What do you think I want? I can say what I want myself: I want AOO (i mean the project and the community) to be treated with respect. Respect, however, is a question of joint discussion and not of one-sided subjugation. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
> On Apr 1, 2020, at 12:55 PM, Jörg Schmidt wrote: > > Hello, > >> -Original Message- >> From: Dave Fisher [mailto:w...@apache.org] >> Sent: Wednesday, April 01, 2020 8:30 PM >> To: dev >> Subject: Re: [discussion] Documentation Contribution based or >> produced by LO? (was: How to join Docs team) >> >> >> >>> On Apr 1, 2020, at 11:11 AM, BMCS wrote: >>> >>> Jörg, your strident proclamations make enemies of those who would be >>> friends of AOO. Many of us, Peter and myself included, >> understand that >>> there can be no reunification, but we seek for cooperation >> between the >>> projects whenever possible. There is no benefit or gain in >> continually >>> resurrecting past animosities and dead issues. >> >> +1. Let’s try to keep the past animosity in the now distant >> past as that is what to my recollection drove Jean to move >> elsewhere during the initial incubation of OpenOffice.org at >> the ASF. The flames on dev@ at that time we equivalent to >> recent wildfires in California and Australia. > > Lies and slander of the past need an apology, only then can they be forgotten. Rob Weir never apologized to me. There are people in this world who never, ever admit to any errors. I’m not one of them. Apologies. While I agree with your sentiment it will not lead to what you want if we keep bringing this issue up. Regards, Dave > > > Jörg > > > - > 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: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
Hello, > -Original Message- > From: Dave Fisher [mailto:w...@apache.org] > Sent: Wednesday, April 01, 2020 8:30 PM > To: dev > Subject: Re: [discussion] Documentation Contribution based or > produced by LO? (was: How to join Docs team) > > > > > On Apr 1, 2020, at 11:11 AM, BMCS wrote: > > > > Jörg, your strident proclamations make enemies of those who would be > > friends of AOO. Many of us, Peter and myself included, > understand that > > there can be no reunification, but we seek for cooperation > between the > > projects whenever possible. There is no benefit or gain in > continually > > resurrecting past animosities and dead issues. > > +1. Let’s try to keep the past animosity in the now distant > past as that is what to my recollection drove Jean to move > elsewhere during the initial incubation of OpenOffice.org at > the ASF. The flames on dev@ at that time we equivalent to > recent wildfires in California and Australia. Lies and slander of the past need an apology, only then can they be forgotten. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
Hello, > -Original Message- > From: BMCS [mailto:b...@apache.org] > Sent: Wednesday, April 01, 2020 8:12 PM > To: dev@openoffice.apache.org > Subject: Re: [discussion] Documentation Contribution based or > produced by LO? (was: How to join Docs team) > The potential new AOO documentation contributor did NOT say that his > contribution would be a copy of the LO Base documentation. yes, you're right. > I suspected > that he might not be aware of "The Apache Way", so I indicated that it > would be advisable to for him to make full disclosure of his > work on the > LO documentation to the AOO project before moving forward. My comment meant something different, namely that the documentation for OOo 3.3.0 is closer to AOO 4.1.7 than any current LO documentation. It is therefore a question of pure expediency to rely on the old OOo documentation. > > We, the ProOO-Box team, are working on the German-language > documentation for AOO, using the English originals of OOo 3.3 > as a basis, which has proven to be very useful. > > That is good news, but how does this help the AOO > Documentation This helps in so far as this documentation is of course also available for use by AOO without restriction. If this were not the case, we would not have noted on the AOO website that we are taking care of the documentation. It is due to the practical situation that there are no uploads on the AOO website yet. This is the concrete situation, but generally (imho): Shouldn't we be grateful for ANY help for AOO? No matter who it comes from? Why do we argue about formalities in times where we lack volunteers? > and why > haven't you Jörg spoken up about this before now? I have, of course, talked about it (years ago), or do you think I work in secret? > > We use the Apache way and this is meritocratic, as we have > been told in other cases over and over again! > What has this to do with a potential new AOO documentation contributor > offering his services. Very simple: here they try to organize the writing of the documentation centrally and this confuses me because all proposals I made in the past have been rejected with reference to the meritocratic approach. I myself am very much in agreement with (centralised) organisation, but this must not lead to certain content issues being promoted and other content issues being hindered. > > It may not be finished yet, but we've been working on the > documentation all the time, where no one else was doing it, > and we've been working as much as we could. > I repeat my previous question: How does this help the AOO > Documentation > and why haven't you Jörg spoken up about this before now? This helps the project, because it makes current (4.x) documentation, also for the project, available in German language. > > So it's not true that nobody would work on the documentation. > > Jörg, please quote the words I wrote, not your distorted > interpretation. Excuse me, but when I refer to Peter's statement, I cannot quote you (Dave). > In other words, VERY LITTLE new or updated material has been added to > the main AOO documentation website pages. Since the main AOO > website is > in English that statement can be taken to mean the English > documentation. > > > greetings, > > Jörg > > Jörg, your strident proclamations make enemies of those who would be > friends of AOO. Many of us, Peter and myself included, understand that > there can be no reunification, but we seek for cooperation between the > projects whenever possible. There is no benefit or gain in continually > resurrecting past animosities and dead issues. I'm for collaboration, but for working together as equals and I'm against any claim of leadership from LO in this collaboration. Several times I was allowed to experience that members of the AOO-community reached out their hand, but LO did not reply. Michael for example speaks of "our friends at LO", but I never read a public statement from the LO-community that spoke of "our friends at AOO". Such things make me wonder. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: How to join Docs team
> -Original Message- > From: Simon Phipps [mailto:webm...@apache.org] > Sent: Wednesday, April 01, 2020 8:04 PM > To: dev > Subject: Re: How to join Docs team > > On Wed, Apr 1, 2020 at 5:32 PM Jörg Schmidt > wrote: > > > Hello, > > > > > From: bmcs [mailto:b...@apache.org] > > > Authors to ODF Authors. The idea being that it would be > one of the few > > > shared areas where AOO and LO could work cooperatively > > > together > > > > I don't believe that at that time, after all the slander > and lies on the > > part of LO, against AOO, cooperation was still possible! > > > > It should never be forgotten how the highest representatives of our > > project (for example Rob Weir) were publicly insulted by > TDF members. > > > > Seriously, can we let it go please? This sort of posting > creates a hostile > environment that discourages participation. Should the culprits at LO apologize to the AOO community for their actions at that time, there will be no need for such contributions from me anymore. There is not a single public statement by the TDF against bashing AOO, and bashing in forums, mailing lists etc. has only one direction in the present: against AOO. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How to join Docs team
On 01/04/2020 19:04, Simon Phipps wrote: > On Wed, Apr 1, 2020 at 5:32 PM Jörg Schmidt wrote: > >> Hello, >> >>> From: bmcs [mailto:b...@apache.org] >>> Authors to ODF Authors. The idea being that it would be one of the few >>> shared areas where AOO and LO could work cooperatively >>> together >> I don't believe that at that time, after all the slander and lies on the >> part of LO, against AOO, cooperation was still possible! >> >> It should never be forgotten how the highest representatives of our >> project (for example Rob Weir) were publicly insulted by TDF members. >> > Seriously, can we let it go please? This sort of posting creates a hostile > environment that discourages participation. > > S. Agreed. I think Dave Fisher's post is a good point at which to closer this thread. Dave - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] Documentation Contribution based or produced by LO? (was: How to join Docs team)
> On Apr 1, 2020, at 11:11 AM, BMCS wrote: > > Jörg, your strident proclamations make enemies of those who would be > friends of AOO. Many of us, Peter and myself included, understand that > there can be no reunification, but we seek for cooperation between the > projects whenever possible. There is no benefit or gain in continually > resurrecting past animosities and dead issues. +1. Let’s try to keep the past animosity in the now distant past as that is what to my recollection drove Jean to move elsewhere during the initial incubation of OpenOffice.org at the ASF. The flames on dev@ at that time we equivalent to recent wildfires in California and Australia. Anyone who contributes in any manner to the whole ODF ecosystem should be welcome within the license constraints. If there is a better place for documentation that must be hosted externally to the ASF by a community member then that is fine with me. Regards, Dave
