Re: POI to be known as Poi?
All, How about puttin' the [VOTE]?? Sincerely, -- Tetsuya ([EMAIL PROTECTED]) -- AIM# tkitahata - On Sun, 20 Jul 2003 12:31:08 +1000 (Subject: POI to be known as Poi? (Was Re: cvs commit: jakarta-poi/src/documentation/content/xdocs historyandfuture.xml)) Glen Stampoultzis <[EMAIL PROTECTED]> wrote: > I've always been unsure whether to refer the POI or Poi. The Poi's have it? > > -- Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI to be known as Poi?
"Details baby, details" said the transvestite in "The Crying Game" (my wife made me watch it) Ha! I just deleted that explanation from the page. That decision was made a looong time ago... Either is acceptable in "speech". If you like abbreviations then its an abbreviation. (Marc liked having both. I wanted the abbreviation for marketing to the open source community that we weren't propagating the file formats, Stefano claims to hate abbreviations) For all sourcecode its POI. I won't budge on this.. Why? Because I don't want to go through all the code and change it I want it to be consistent... And I'd LIKE to think we have better things to do. Additionally I like it all caps for another reason. In portuguese and some other languages "poi" is a word like "for" or "or" or something... To see this google on "poi" rather than "jakarta POI" and see what you get. (google isn't case sensitive but other things are). In any case. Lets just de-emphasize what the abbreviations mean (if you couldn't figure out that¹s what I'm trying to do). This is the important issue. I really would prefer if we didn't have votes except on really important stuff. I think its totally fine if Tetsuya wants to put "Poi" in the docs as the title. Lets not sweat the details... :-) -Andy On 7/19/03 11:00 PM, "Tetsuya Kitahata" <[EMAIL PROTECTED]> wrote: > All, > > How about puttin' the [VOTE]?? > > Sincerely, > > -- Tetsuya ([EMAIL PROTECTED]) -- AIM# tkitahata > > - > > On Sun, 20 Jul 2003 12:31:08 +1000 > (Subject: POI to be known as Poi? (Was Re: cvs commit: > jakarta-poi/src/documentation/content/xdocs historyandfuture.xml)) > Glen Stampoultzis <[EMAIL PROTECTED]> wrote: > >> I've always been unsure whether to refer the POI or Poi. The Poi's have it? >> >> -- Glen > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI to be known as Poi?
On Sat, 19 Jul 2003 23:14:10 -0400 "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: > "Details baby, details" said the transvestite in "The Crying Game" (my wife > made me watch it) "transvestite" ... what are you talking about? :D Have I to change my name from "Tetsuya" to "Tetsuo"? :D > For all sourcecode its POI. I won't budge on this.. Why? Because I don't > want to go through all the code and change it I want it to be > consistent... And I'd LIKE to think we have better things to do. I have *nice* text editor which can perform the permutation usin' regexp. If we have *consensus* on this issue, I can perform this soon. > Additionally I like it all caps for another reason. In portuguese and some > other languages "poi" is a word like "for" or "or" or something... To see > this google on "poi" rather than "jakarta POI" and see what you get. > (google isn't case sensitive but other things are). Oh, google issue... In a month or around, you'll be able to find poi website using "Java XML" via google, I am sure. > In any case. Lets just de-emphasize what the abbreviations mean (if you > couldn't figure out that¹s what I'm trying to do). This is the important > issue. yep > I really would prefer if we didn't have votes except on really important > stuff. I think its totally fine if Tetsuya wants to put "Poi" in the docs > as the title. Lets not sweat the details... :-) I'll convert them (docs) within a few days, then. "POI" <-> "Poi": either case is okay. > On 7/19/03 11:00 PM, "Tetsuya Kitahata" <[EMAIL PROTECTED]> wrote: > > > All, > > > > How about puttin' the [VOTE]?? > > > > Sincerely, > > > > -- Tetsuya ([EMAIL PROTECTED]) -- AIM# tkitahata > > > > - > > > > On Sun, 20 Jul 2003 12:31:08 +1000 > > (Subject: POI to be known as Poi? (Was Re: cvs commit: > > jakarta-poi/src/documentation/content/xdocs historyandfuture.xml)) > > Glen Stampoultzis <[EMAIL PROTECTED]> wrote: > > > >> I've always been unsure whether to refer the POI or Poi. The Poi's have it? > >> > >> -- Glen Sincerely, -- Tetsuya ([EMAIL PROTECTED]) -- AIM# tkitahata P.S. By the way, "Horrible" -> "Humble" might be better .. IMHO :D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI to be known as Poi?
I must admit I'm a bit concerned that this issue is taking conversational precedent over the issue of making HSSF performance much nicer. That being said, this is obviously important to you guys so I'll do my best although you know these types of conversations generally make me uncomfortable because they often consume a great deal of time and can grow numerous. I'd rather leave things like they are minus the descriptions (asides from the marketing issue there are other issues I'd rather not discuss yet that will hopefully be settled this week). Either is acceptable, POI is preferable to me and is the only acceptable way to name classes (because that¹s the way it is presently and its silly to change it and break everything just for such a small thing). POI, Poi, PoI, pOi are all personal preference. In the case of personal preference I almost always vote for the status quo or the liberal view of "whatever floats your boat" provided it isn't disruptive. Renaming all of the class files would be disruptive. Going and changing all the comments would be disruptive. Having the documentation talk about Poi where all the code talks about POI would be incongruent. And changing everything to Poi where ALL the articles on all of the internet, every link, etc talks about POI...draw your own conclusions. However if you want to call it Poi, call it Poi. We have a brand, we may or may not like its capitalization, but establishing a new brand is kind of painful. No one calls POI "poor obfuscation implementation" except for me when I talk about it in front of crowds and they laugh If the definition isn't on the page...no one will know what it means and its all fine. I still may tell people when I want a laugh or the old Stallmanesque argument (DO NOT SLASHDOT ME ANYONE!) about "you're propagating the proprietary file format" is pulled from the dusty bookshelf.** -Andy POI was named around the same time Stallman wrote his article about refusing word documents...and I thought "this guy doesn't ever have to deal with business clients and it shows". The name was intended to be not only humorous but appeal to the open source community and make this argument sound kind of silly. (Guys who call it Horrible Spreadsheet format cannot really be accused of propagating it can they?) On 7/19/03 11:56 PM, "Tetsuya Kitahata" <[EMAIL PROTECTED]> wrote: > On Sat, 19 Jul 2003 23:14:10 -0400 > "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: > >> "Details baby, details" said the transvestite in "The Crying Game" (my wife >> made me watch it) > > "transvestite" ... what are you talking about? :D > > > Have I to change my name from "Tetsuya" to "Tetsuo"? :D > > >> For all sourcecode its POI. I won't budge on this.. Why? Because I don't >> want to go through all the code and change it I want it to be >> consistent... And I'd LIKE to think we have better things to do. > > I have *nice* text editor which can perform the permutation usin' regexp. > If we have *consensus* on this issue, I can perform this soon. > >> Additionally I like it all caps for another reason. In portuguese and some >> other languages "poi" is a word like "for" or "or" or something... To see >> this google on "poi" rather than "jakarta POI" and see what you get. >> (google isn't case sensitive but other things are). > > Oh, google issue... In a month or around, you'll be able to find poi > website using "Java XML" via google, I am sure. > >> In any case. Lets just de-emphasize what the abbreviations mean (if you >> couldn't figure out that¹s what I'm trying to do). This is the important >> issue. > > yep > >> I really would prefer if we didn't have votes except on really important >> stuff. I think its totally fine if Tetsuya wants to put "Poi" in the docs >> as the title. Lets not sweat the details... :-) > > I'll convert them (docs) within a few days, then. > "POI" <-> "Poi": either case is okay. > >> On 7/19/03 11:00 PM, "Tetsuya Kitahata" <[EMAIL PROTECTED]> wrote: >> >>> All, >>> >>> How about puttin' the [VOTE]?? >>> >>> Sincerely, >>> >>> -- Tetsuya ([EMAIL PROTECTED]) -- AIM# tkitahata >>> >>> - >>> >>> On Sun, 20 Jul 2003 12:31:08 +1000 >>> (Subject: POI to be known as Poi? (Was Re: cvs commit: >>> jakarta-poi/src/documen
Re: POI to be known as Poi?
On Sat, 19 Jul 2003 23:14:10 -0400 "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: > I really would prefer if we didn't have votes except on really important > stuff. I think its totally fine if Tetsuya wants to put "Poi" in the docs > as the title. Lets not sweat the details... :-) Names are important and justify a vote. Best regards Rainer Klute Rainer Klute IT-Consulting GmbH Dipl.-Inform. Rainer Klute E-Mail: [EMAIL PROTECTED] Körner Grund 24 Telefon: +49 172 2324824 D-44143 Dortmund Telefax: +49 231 5349423 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POI to be known as Poi?
(BOkay! let's have a vote! (B (B-- Tetsuya ([EMAIL PROTECTED]) (B (BOn Fri, 25 Jul 2003 00:44:03 +0200 (B(Subject: Re: POI to be known as Poi?) (BRainer Klute <[EMAIL PROTECTED]> wrote: (B (B> On Sat, 19 Jul 2003 23:14:10 -0400 "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: (B> > I really would prefer if we didn't have votes except on really important (B> > stuff. I think its totally fine if Tetsuya wants to put "Poi" in the docs (B> > as the title. Lets not sweat the details... :-) (B> (B> Names are important and justify a vote. (B> (B> Best regards (B> Rainer Klute (B> (B>Rainer Klute IT-Consulting GmbH (B> Dipl.-Inform. (B> Rainer Klute E-Mail: [EMAIL PROTECTED] (B> Kvrner Grund 24 Telefon: +49 172 2324824 (B> D-44143 Dortmund Telefax: +49 231 5349423 (B (B (B- (BTo unsubscribe, e-mail: [EMAIL PROTECTED] (BFor additional commands, e-mail: [EMAIL PROTECTED]
POI to be known as Poi? (Was Re: cvs commit: jakarta-poi/src/documentation/content/xdocs historyandfuture.xml)
I've always been unsure whether to refer the POI or Poi. The Poi's have it? -- Glen At 11:45 AM 20/07/2003, you wrote: tetsuya 2003/07/19 18:45:51 Modified:src/documentation/content/xdocs historyandfuture.xml Log: POI -> Poi Revision ChangesPath 1.4 +13 -13jakarta-poi/src/documentation/content/xdocs/historyandfuture.xml Index: historyandfuture.xml === RCS file: /home/cvs/jakarta-poi/src/documentation/content/xdocs/historyandfuture.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- historyandfuture.xml 20 Jul 2003 01:37:30 - 1.3 +++ historyandfuture.xml 20 Jul 2003 01:45:50 - 1.4 @@ -14,7 +14,7 @@ Jakarta Poi - Brief Project History -The POI project was dreamed up back around April 2001, when +The Poi project was dreamed up back around April 2001, when Andrew Oliver landed a short term contract to do Java-based reporting to Excel. He'd done this project a few times before and knew right where to look for the tools he needed. @@ -41,18 +41,18 @@ on Marc's library. Several users wrote in asking to read XLS (not just write as had originally been planned) and one user had special requests for a different use for POIFS. Before -long, the project scope had tripled. POI 1.0 was released a +long, the project scope had tripled. Poi 1.0 was released a month later than planned, but with far more features. Marc quickly wrote the serializer framework and HSSF Serializer in record time and Andrew banged out more documentation and worked on making people aware of the project - Shortly before the release, POI was fortunate to come into + Shortly before the release, Poi was fortunate to come into contact with Nicola -Ken- Barrozzi who gave them samples for the HSSF Serializer and help uncover its unfortunate bugs (which were promptly fixed). More recently, Ken ported most - of the POI project documentation to XML from Andrew's crappy + of the Poi project documentation to XML from Andrew's crappy HTML docs he wrote with Star Office. @@ -60,7 +60,7 @@ joined the project. Glen was ticked off at Andrew's flippant attitude towards adding graphing to HSSF. Glen got so ticked off he decided to grab a hammer and do it himself. Glen has already become an integral -part of the POI development community; his contributions to HSSF have +part of the Poi development community; his contributions to HSSF have already started making waves. @@ -69,16 +69,16 @@ Cocoon Project, only to discover the project had outgrown fitting nicely into just Cocoon long ago. Furthermore, Andrew started eyeing other projects he'd like to - see POI functionality added to. So it was decided to donate - the Serializers and Generators to Cocoon, other POI - integration components to other projects, and the POI APIs + see Poi functionality added to. So it was decided to donate + the Serializers and Generators to Cocoon, other Poi + integration components to other projects, and the Poi APIs would become part of Jakarta. It was a bumpy road but it looks like everything turned out since you're reading this! -What's next for POI +What's next for Poi HSSF, during the 2.0 cycle, will undergo a few @@ -114,8 +114,8 @@ hoping to add support for formulas during this cycle. We're beginning to expand our scope yet again. If we could -do all of this for XLS files, what about Doc files or PPT -files? We're thinking that our next component (HWSF - Manipulates +do all of this for XLS files, what about Doc files or PowerPoint +files? We're thinking that our next component (HWPF - Manipulates Word Processor Format) should follow the same pattern. We're hoping that new blood will join the team and allow us to tackle this even faster (in part because POIFS is already finished). But - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/
