review requested: [Issue 118023] Calc: Cut-and-paste between spreadsheets causes incorrect cell reference changes : [Attachment 85284] Hack: skip reference updates for inter-document clipboard paste
dam...@apache.org has asked for review: Issue 118023: Calc: Cut-and-paste between spreadsheets causes incorrect cell reference changes https://bz.apache.org/ooo/show_bug.cgi?id=118023 Attachment 85284: Hack: skip reference updates for inter-document clipboard paste https://bz.apache.org/ooo/attachment.cgi?id=85284&action=edit --- Comment #6 from dam...@apache.org --- Created attachment 85284 --> https://bz.apache.org/ooo/attachment.cgi?id=85284&action=edit Hack: skip reference updates for inter-document clipboard paste This hack fixes the bug for me. By not performing reference updates when it's an inter-document paste (the "pCBFCP->pClipDoc->GetClipParam().getSourceDocID() == GetDocumentID()" is false), the reference stays correct instead of referencing the pasted cell. However I am not sure how reference updates work in general - the ScDocument::UpdateReference() function seems to do a lot, affecting chart references, area links, validation lists, etc. - so I am not sure what else could break... Can somebody more familiar with Calc's internals please weigh in on whether this approach is right? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Open office spreadsheets
Seems these issue is solved in 4.1 https://blogs.apache.org/OOo/entry/apache_openoffice_4_1_to since is a new feature there could be some QA issues being filed. On 7/23/14, G Owen wrote: > Hi all at Open office > I have been using office 2007 for some time, but would like to use your > softwatre in future. > I am having trouble with the spreadsheets, as I can't get Jaws to read what > is in the cells! > Is there a fix for this? Or am I doing some thing wrong? > Many thanks > G > -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Open office spreadsheets
Hi all at Open office I have been using office 2007 for some time, but would like to use your softwatre in future. I am having trouble with the spreadsheets, as I can't get Jaws to read what is in the cells! Is there a fix for this? Or am I doing some thing wrong? Many thanks G
Linked fomulas to other xls spreadsheets stopped working
Hi there, I have been using your OpenOffice for many years now and I always save my files as XLS format. I have link formulas between weeksheets and they worked OK in the past. Today when I open my files and accept the update links prompt from the file that contains the links, my links now show the #Ref errors. I tried creating the link again but it doesn't work except if my link is to a cell that contains text, if the cell contains formula, no longer works. I down loaded your newest version 4.1, repeated all the steps and same thing happens. I then tried saving the source file as the ods format and update the links, keeping the target file as Xls format, that seems to fix the issue. I then tried to change the source file back to Xls and update the links, same issue occurred. Is this a bug? I have Window Vista. If you need more info, please let me know. Please look into this. Thank you for the free products and looking into this issue. Diana
Re: Spreadsheets
Forwarding the answer (below) to Rose who is not subscribed. Andrea Alexandro Colorado wrote: You need to set up OpenOffice as a default application for ODS, XLS, XLSX. OpenOffice does this for you by default when you install it on your computer under this dialog: https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Getting_Started/File_associations If you miss that chanced and AOO is already on your box, making the association manually should be done from the windows side. Here is a process on how Windows 8 do file association: http://winsupersite.com/article/windows8/windows-8-tip-change-file-associations-144102 On Mon, Feb 3, 2014 at 8:46 AM, wrote: Good Afternoon Please accept my apologies if I have sent this to the wrong department but I have tried all the information pages to see if they could help before contacting anyone and I am struggling to find an answer to my problem, I have subscribed to Open Office for a long time and have never had any problems - up to two weeks ago I had a Dell PC with Vista on and Open Office worked fine on that I had some emails with Spreadsheets attached and they opened fine on Windows 8 but now if I try that all I get is the file option asking me to choose a program from the list to save it in - and Open Office is not one of them Why are the Spreadsheets not saving - I put in save to ODF but to no effect, I just do not know how to correct this I would appreciate any help with this Many thanks & Kind Regards Rose Galloway - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spreadsheets
You need to set up OpenOffice as a default application for ODS, XLS, XLSX. OpenOffice does this for you by default when you install it on your computer under this dialog: https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Getting_Started/File_associations If you miss that chanced and AOO is already on your box, making the association manually should be done from the windows side. Here is a process on how Windows 8 do file association: http://winsupersite.com/article/windows8/windows-8-tip-change-file-associations-144102 On Mon, Feb 3, 2014 at 8:46 AM, wrote: > > Good Afternoon > > Please accept my apologies if I have sent this to the wrong department but > I have tried all the information pages to see if they could help > before contacting anyone and I am struggling to find an answer to my > problem, > > I have subscribed to Open Office for a long time and have never had any > problems - up to two weeks ago I had a Dell PC with Vista on and > Open Office worked fine on that > > I had some emails with Spreadsheets attached and they opened fine on > Windows 8 but now if I try that all I get is the file option asking me > to choose a program from the list to save it in - and Open Office is not > one of them > > Why are the Spreadsheets not saving - I put in save to ODF but to no > effect, I just do not know how to correct this > > I would appreciate any help with this > > Many thanks & Kind Regards > > Rose Galloway > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614
Spreadsheets
Good Afternoon Please accept my apologies if I have sent this to the wrong department but I have tried all the information pages to see if they could help before contacting anyone and I am struggling to find an answer to my problem, I have subscribed to Open Office for a long time and have never had any problems - up to two weeks ago I had a Dell PC with Vista on and Open Office worked fine on that I had some emails with Spreadsheets attached and they opened fine on Windows 8 but now if I try that all I get is the file option asking me to choose a program from the list to save it in - and Open Office is not one of them Why are the Spreadsheets not saving - I put in save to ODF but to no effect, I just do not know how to correct this I would appreciate any help with this Many thanks & Kind Regards Rose Galloway
Re: Number of spreadsheets limitation
>but MS Excel manages much >more than that (I still don't know the limit, but we have here a file >with 336 spreadsheets, which cannot be opened in OO 4.0.1 without loss). https://issues.apache.org/ooo/show_bug.cgi?id=35901 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Number of spreadsheets limitation
Good afternoon. Since we are in an effort to erradicate MS Office from our business, I have a suggestion that may be very simple to fix for future releases: the max number of spreadsheets. The number of spreadsheets is now limited to 256 (byte) for release 4.0.1, but MS Excel manages much more than that (I still don't know the limit, but we have here a file with 336 spreadsheets, which cannot be opened in OO 4.0.1 without loss). I know it can affect the amount of memory used, but, maybe, not that much. Thanks a lot for hearing me. Have a nice job! -- Untitled Document Thanks a lot! **Nota sobre homologações:* A homologação de documentos de Compensação ou Arrecadação junto aos bancos e agentes arrecadadores serve apenas para garantir que as informações necessárias ao recebimento dos pagamentos estejam corretas, ou seja, que o valor pago seja depositado na conta esperada. Logo,/*é um documento de responsabilidade do cliente*/, já que este é o interessado em receber. A IMC orienta que todo novo documento ou emissão de taxa anual ou esporádica seja homologado a fim de garantir que as informações fornecidas pelas empresas processadoras de dados e as impressas correspondam às esperadas pelos bancos/agentes arrecadadores, *mas não obrigam a homologar*. No entanto, a IMC NÂO PODE SER RESPONSABILIZADA pelo não recebimento ou recebimento errôneo de documentos pela falta de homologação. Com exceção da CAIXA, que exige documentos impressos pela gráfica emitente, *as homologações nos demais bancos/agentes arrecadadores são de responsabilidade do CLIENTE*, devendo este entrar em contato com seus gerentes de conta solicitando orientações. *CAIXA:* A IMC envia as amostras IMPRESSAS (por exigência da CAIXA) para a Central Regional da CAIXA correspondente à agência recebedora do clinte, devendo o resultado ser retirado pelo próprio cliente junto à sua agência recebedora em um prazo que varia entre 2 e 5 dias úteis. *BANCO DO BRASIL:* é necessário que, antes do envio, o CLIENTE abra um protocolo de HOMOLOGAÇÃO DE DOCUMENTO DE COBRANÇA pelo telefone 0800 729 0500. Então, de posse do nº do protocolo e do endereço de e-mail fornecidos, remeta o arquivo contendo os documentos (anexado ao e-mail), o qual já está preparado no tamanho e formato exigidos pelo banco. *DEMAIS BANCOS:* entre em contato com seu gerente buscando orientações para homologação. Atenciosamente, Gabriel Tavares de Oliveira Castellani Gerente de Desenvolvimento *IMC Gráfica Ltda. Grafimac Gráfica Ltda. * Av. Santos Dummont, 2.425 89219-731 - Joinville - SC - Brasil Telefone: (47) 3437-4279 Celular: (47) 9658-6846 E-mail/MSN: mailto:gabr...@imcimpressos.com.br>>
Re: Easy one on spreadsheets
Check the zoom in View menu - Mail original - De: robertdocholli...@gmail.com À: dev@openoffice.apache.org Envoyé: Mardi 19 Mars 2013 19:14:03 Objet: Easy one on spreadsheets On Spread sheets my default makes my spread sheet cell very small How can i reset to the original default for cell size thanks - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Implementation-defined behaviors in ODF spreadsheets
On 13/02/2013 Rob Weir wrote: This lead to a series of behaviors which were specified to be "implementation-defined", or in some case "locale-defined" or "unspecified". These are subtly different, and express nuances common in standards, what we refer to as "dimensions of variability". And where does OpenOffice document its choices? In OpenDocument-v1.2-cd05-part2 2.3 I read: "Applications should document all implementation-defined and variances from this standard in a manner that the application users can obtain the information (e.g., in the application help for the relevant function)." If we have nothing, starting a wiki page seems a better option than integrating the application help right now. If we ever do go to a warning mode in Calc, where users are warned about potential calculation issues, these would probably be ones that we would check for. This is not going to happen soon, but by 4.0, especially if we want to advertise the better ODF compliance we'll have by then, our implementation-defined behavior should be documented. Regards, Andrea.
Re: Implementation-defined behaviors in ODF spreadsheets
Awesome! On 02/13/2013 12:43 PM, Rob Weir wrote: This topic seems to be of more general interest, given the discussions we've been having regarding the evaluation of 0^0. When we were writing up the specification of ODF 1.2's OpenFormula we had the goal to describe how real-world spreadsheet applications worked today. Where they worked the same then we wrote up in detail how they worked. Where there was variance among implementations then we tried to describe the bounds within which current applications behaved. So our work was mainly descriptive. There is not a stick big enough to force (at that time) Sun, Microsoft, IBM, Google as well as Gnumeric and KSpread (now Calligra) to change their implementations. This lead to a series of behaviors which were specified to be "implementation-defined", or in some case "locale-defined" or "unspecified". These are subtly different, and express nuances common in standards, what we refer to as "dimensions of variability". The W3C has a note on the topic: http://www.w3.org/TR/spec-variability/ But essentially, standardizers try to strike a balance between interoperability and cost to implement a standard. Even with physical standards, say for a screw or a bolt, there are tolerances give. The screw must have a length of 3cm +/- 0.1mm, for example. If the tolerance were set much higher then the cost to conform would skyrocket, but the incremental interop benefits would diminish. So the art of standardization the art of finding the right balance. This is political also, so it is also in the realm of the "art of the possible" in any given time and place. So when putting together OpenFormula I created a spreadsheet to collect together the 61 implementation-defined or unspecified behaviors in OpenFormula. If any is really interested in this area I'd recommend reviewing this spreadsheet. It is a lot easier/faster than reading the ODF 1.2 specification: http://markmail.org/thread/iz2gggmwednmchqe If we ever do go to a warning mode in Calc, where users are warned about potential calculation issues, these would probably be ones that we would check for. Regards, -Rob -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt Info: http://www.pitonyak.org/oo.php
Re: Implementation-defined behaviors in ODF spreadsheets
Am 02/13/2013 06:43 PM, schrieb Rob Weir: This topic seems to be of more general interest, given the discussions we've been having regarding the evaluation of 0^0. When we were writing up the specification of ODF 1.2's OpenFormula we had the goal to describe how real-world spreadsheet applications worked today. Where they worked the same then we wrote up in detail how they worked. Where there was variance among implementations then we tried to describe the bounds within which current applications behaved. So our work was mainly descriptive. There is not a stick big enough to force (at that time) Sun, Microsoft, IBM, Google as well as Gnumeric and KSpread (now Calligra) to change their implementations. This lead to a series of behaviors which were specified to be "implementation-defined", or in some case "locale-defined" or "unspecified". These are subtly different, and express nuances common in standards, what we refer to as "dimensions of variability". The W3C has a note on the topic: http://www.w3.org/TR/spec-variability/ But essentially, standardizers try to strike a balance between interoperability and cost to implement a standard. Even with physical standards, say for a screw or a bolt, there are tolerances give. The screw must have a length of 3cm +/- 0.1mm, for example. If the tolerance were set much higher then the cost to conform would skyrocket, but the incremental interop benefits would diminish. So the art of standardization the art of finding the right balance. This is political also, so it is also in the realm of the "art of the possible" in any given time and place. So when putting together OpenFormula I created a spreadsheet to collect together the 61 implementation-defined or unspecified behaviors in OpenFormula. If any is really interested in this area I'd recommend reviewing this spreadsheet. It is a lot easier/faster than reading the ODF 1.2 specification: http://markmail.org/thread/iz2gggmwednmchqe If we ever do go to a warning mode in Calc, where users are warned about potential calculation issues, these would probably be ones that we would check for. Thanks a lot for showing us what else is not "written in stone" but depends on the respective application how it is implemented. 61 is an impressively high number. Besides a feasible warning mode, maybe it's also possible to bring the high number down and with the remaining stuff we could create a new options tabpage, to leave it to the (power) user what result she/he would like to have. The default value (e.g., 1) and the other posibilities (e.g., 0, error) could be described in help topics, so that the users can look by themselves why AOO is showing this result / error. Marcus
RE: Implementation-defined behaviors in ODF spreadsheets
+1 -Original Message- From: Rob Weir [mailto:robw...@apache.org] Sent: Wednesday, February 13, 2013 09:44 To: dev@openoffice.apache.org Subject: Implementation-defined behaviors in ODF spreadsheets This topic seems to be of more general interest, given the discussions we've been having regarding the evaluation of 0^0. When we were writing up the specification of ODF 1.2's OpenFormula we had the goal to describe how real-world spreadsheet applications worked today. Where they worked the same then we wrote up in detail how they worked. Where there was variance among implementations then we tried to describe the bounds within which current applications behaved. So our work was mainly descriptive. There is not a stick big enough to force (at that time) Sun, Microsoft, IBM, Google as well as Gnumeric and KSpread (now Calligra) to change their implementations. This lead to a series of behaviors which were specified to be "implementation-defined", or in some case "locale-defined" or "unspecified". These are subtly different, and express nuances common in standards, what we refer to as "dimensions of variability". The W3C has a note on the topic: http://www.w3.org/TR/spec-variability/ But essentially, standardizers try to strike a balance between interoperability and cost to implement a standard. Even with physical standards, say for a screw or a bolt, there are tolerances give. The screw must have a length of 3cm +/- 0.1mm, for example. If the tolerance were set much higher then the cost to conform would skyrocket, but the incremental interop benefits would diminish. So the art of standardization the art of finding the right balance. This is political also, so it is also in the realm of the "art of the possible" in any given time and place. So when putting together OpenFormula I created a spreadsheet to collect together the 61 implementation-defined or unspecified behaviors in OpenFormula. If any is really interested in this area I'd recommend reviewing this spreadsheet. It is a lot easier/faster than reading the ODF 1.2 specification: http://markmail.org/thread/iz2gggmwednmchqe If we ever do go to a warning mode in Calc, where users are warned about potential calculation issues, these would probably be ones that we would check for. Regards, -Rob
Implementation-defined behaviors in ODF spreadsheets
This topic seems to be of more general interest, given the discussions we've been having regarding the evaluation of 0^0. When we were writing up the specification of ODF 1.2's OpenFormula we had the goal to describe how real-world spreadsheet applications worked today. Where they worked the same then we wrote up in detail how they worked. Where there was variance among implementations then we tried to describe the bounds within which current applications behaved. So our work was mainly descriptive. There is not a stick big enough to force (at that time) Sun, Microsoft, IBM, Google as well as Gnumeric and KSpread (now Calligra) to change their implementations. This lead to a series of behaviors which were specified to be "implementation-defined", or in some case "locale-defined" or "unspecified". These are subtly different, and express nuances common in standards, what we refer to as "dimensions of variability". The W3C has a note on the topic: http://www.w3.org/TR/spec-variability/ But essentially, standardizers try to strike a balance between interoperability and cost to implement a standard. Even with physical standards, say for a screw or a bolt, there are tolerances give. The screw must have a length of 3cm +/- 0.1mm, for example. If the tolerance were set much higher then the cost to conform would skyrocket, but the incremental interop benefits would diminish. So the art of standardization the art of finding the right balance. This is political also, so it is also in the realm of the "art of the possible" in any given time and place. So when putting together OpenFormula I created a spreadsheet to collect together the 61 implementation-defined or unspecified behaviors in OpenFormula. If any is really interested in this area I'd recommend reviewing this spreadsheet. It is a lot easier/faster than reading the ODF 1.2 specification: http://markmail.org/thread/iz2gggmwednmchqe If we ever do go to a warning mode in Calc, where users are warned about potential calculation issues, these would probably be ones that we would check for. Regards, -Rob
