Please, add CT2N Extension (Convert text to numbers) to LibreOffice installation. http://extensions.services.openoffice.org/project/CT2N
Created attachment 48145 [details] System Independent Extension
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Please, add CT2N Extension (Convert text to numbers) to LibreOffice installation. http://extensions.libreoffice.org/extension-center/ct2n-convert-text-to-number-and-dates This extension (or functions of this extension) is not present in the 3.5.0 beta1 or beta2 prereleases.
*** Bug 67342 has been marked as a duplicate of this bug. ***
*** Bug 65312 has been marked as a duplicate of this bug. ***
Tomaz - for me the extension is broken, can you confirm this? Debating if I should open a new bug - on 4.0.5 I get an error on installation, on 4.1.2 it installs but won't do anything.
It installs on LO daily but it does not work - nothing gets converted. Anyway.. my intention is to implement the same thing as CT2N extension does directly into Calc as this should be fairly easy to do. Regards, Tomaž
@Cor: CT2N is accused to be not working on master ;-)
I see it does not start from the toolbar. Alt-F11 .. MyMacros > CT2N > MainCode > StartHere does work .. Hmm..
Hi Tomaz, (In reply to comment #7) > Anyway.. my intention is to implement the same thing as CT2N extension does > directly into Calc as this should be fairly easy to do. Prolly ;) I have some additional suggestions from users, that I did not yet came up too. So pls contact me if you are that far.
Having "Data -> Text to Columns..." already in Calc, I wonder if there is something / anything _additional_ that the CT2N extension can do. While importing from a csv / text file, we can also select columns and set a format. Perhaps it would be better to improve those 2 features (or are those 2 actually the same feature?) with more options / controls for different number formats, instead of investing time in an alternative extension that might not bring anything really new?
Ady, CT2N allows to find cell content that looks like a number or date but was entered as text and therefor is not considered as number in calculations and offers to convert such content to numeric cell content. While TextToColumn can be used to convert text to numbers, finding such values and offering a proper conversion in a way convenient to the user is what is needed.
(In reply to comment #9) > I see it does not start from the toolbar. > Alt-F11 .. MyMacros > CT2N > MainCode > StartHere does work .. > > Hmm.. Confirm the behaviour in 4.2.0.alpha1. Probably an implementation of the toolbar that is not OK and breaks now. (LibreLex doesn't have the problem - need to look into it.)
(In reply to comment #10) > Prolly ;) > I have some additional suggestions from users, that I did not yet came up > too. So pls contact me if you are that far. Also: there is no real change for me to do the implementation somewhere the next years. So great if you or someone else picks this up !
*** Bug 62145 has been marked as a duplicate of this bug. ***
*** Bug 83077 has been marked as a duplicate of this bug. ***
*** Bug 91399 has been marked as a duplicate of this bug. ***
*** Bug 99374 has been marked as a duplicate of this bug. ***
As one can see from all these dupes coming up, it seems to be something wished by the public and an important improvement. The problem is a showstopper for the non-computer-savvy and is still quite annoying for the geeks. For this issue, it is not at all important if ct2n is working or not. A different - and maybe even more elegant - way to achieve the same goal would be to modify the import functionality. I could detect columns, the content of which is put between quotation marks and ask the user, if they should be removed during import. This could even be the default setting, with no disadvantages coming to my mind. Thus, the whole problem would be avoided in the first place.
Addendum: I mean of course the quotation marks be removed, not the columns. Best would be to spread the word to somebody, who knows the import functionality well and for whom it would be a comparatively small effort to implement such an "ignore quotes" pathway.
Note we don't have "show stoppers" - we have an open source (and free) product that users "take it as they get it." If it's a show stopper, no one will be offended if those users use another product that fit their needs better. There are no paid developers under TDF, no one gives orders, it doesn't really matter how many users want an enhancement. The only way this gets done is if a volunteer finds it interesting enough to implement - I suspect this will take a long long time (and likely will never be done)
I did not intend to offend anybody and am sorry if what i wrote came across like an offense. Maybe as a non english speaker i was not so aware of the strong negative connotations of the word "showstopper". I am well aware of this old question "Am i entitled to this or that improvement in a software or not.", and clearly the answer is "not", as i did not pay for it (even if i actually donated a small amount of money). OTOH i can imagine, that some developers might be interested in feedback, to just learn, what feature or problem is important to the users out there, who are no geeks. And yes, as i happened to stumble over this issue, i egoistically find arguments why exactly this issue is important. I am honestly convinced that it would be an improvement for a lot of people. If those arguments trigger a discussion - the better.
No need to apologize! My bad - I just want to keep expectations real :) We love user feedback but sometimes users have false expectations of what is to come so I just like to clarify. No offense taken/meant and I'm happy to see users requesting this (I'd love the feature too! I wish I had the skills and/or time to implement). FWIW I poked the creator of the extension some time ago and he wasn't able to add it directly to the code so....that channel is out