Re: [fossil-users] Markdown engine integrated into fossil
On 2012-07-09 15:41, Richard Hipp wrote: On Mon, Jul 9, 2012 at 3:31 AM, Baptiste Daroussin baptiste.darous...@gmail.com [6] wrote: 2012/6/7 Richard Hipp d...@sqlite.org [1]: My priority is to get WYSIWYG wiki editing going, at which point the underlying wiki formatting language becomes largely irrelevant, no? Far from criticising your decision to write such an editor, I offer the observation that If a markdown jquery editor would be used, then the available markdown library could be used for rendering, jquery for client side Since we are using it anyway. Those wysiwyg markdown editors are available and leave us only with interfacing/integration. The maintenance burden on the editor is not with us And, maybe, we can offer a migration path for existing wiki and/or embedded documentation? D. Richard Hipp d...@sqlite.org [5] -- Rene ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
2012/6/7 Richard Hipp d...@sqlite.org: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! Reading at the feeback from Munich, this obviously didn't happened :) is there still plan on it, (btw the library seems to have been fully renamed to libsoldout) Sorry for insisting on this features, but I would love so much to be able to write my documentation in markdown :D regards, Bapt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Mon, Jul 9, 2012 at 3:31 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: 2012/6/7 Richard Hipp d...@sqlite.org: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! Reading at the feeback from Munich, this obviously didn't happened :) Yeah. Unfortunately, no actual code writing took place at the code sprint. Though lots of cool ideas were exchanged and developed! is there still plan on it, (btw the library seems to have been fully renamed to libsoldout) There are lots of nice features that people want, but I have limited time to work on them. Perhaps there can be volunteers. My priority is to get WYSIWYG wiki editing going, at which point the underlying wiki formatting language becomes largely irrelevant, no? Sorry for insisting on this features, but I would love so much to be able to write my documentation in markdown :D regards, Bapt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
2012/7/9 Richard Hipp d...@sqlite.org: On Mon, Jul 9, 2012 at 3:31 AM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: 2012/6/7 Richard Hipp d...@sqlite.org: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! Reading at the feeback from Munich, this obviously didn't happened :) Yeah. Unfortunately, no actual code writing took place at the code sprint. Though lots of cool ideas were exchanged and developed! Yeah I've seen that :). is there still plan on it, (btw the library seems to have been fully renamed to libsoldout) There are lots of nice features that people want, but I have limited time to work on them. Perhaps there can be volunteers. She volunteers and did the job :) My priority is to get WYSIWYG wiki editing going, at which point the underlying wiki formatting language becomes largely irrelevant, no? Not for me as I want to use in trunk documentation, and edit it with my favorite $EDITOR :) WYSIWYG doesn't fit my needs at all, plus I have some automated chains using markdown, so having my documentation written only once would be great. Anyway I can wait or live without it, just it will easier maintaining some of my projects. regards, Bapt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Mon, Jul 9, 2012 at 3:41 PM, Richard Hipp d...@sqlite.org wrote: Yeah. Unfortunately, no actual code writing took place at the code sprint. Though lots of cool ideas were exchanged and developed! i think this particular one probably got forgotten because none of those present are among the markdown advocates :/. My priority is to get WYSIWYG wiki editing going, at which point the underlying wiki formatting language becomes largely irrelevant, no? If we do the custom pages first, wysiwyg could be built as a custom page (i think). i'm still hashing out ideas on paper for those, but two separate hand/elbow ailments (one right, one left) have been slowing me down the past few days :(. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
Hello, on Thursday 07 June 2012 at 12:14, Richard Hipp wrote: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! I was considering keeping the markdown branch in my public clone of fossil by merging recent commits from trunk. Would it be useful or harmful or irrelevant? Natacha pgp8HTZHJdYqk.pgp Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Fri, Jun 8, 2012 at 3:30 AM, Natacha Porté nata...@instinctive.euwrote: Hello, on Thursday 07 June 2012 at 12:14, Richard Hipp wrote: On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! I was considering keeping the markdown branch in my public clone of fossil by merging recent commits from trunk. Would it be useful or harmful or irrelevant? Useful. Natacha ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
Is there any status on this? rejected ? still under review ? regards, Bapt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Thu, Jun 7, 2012 at 12:10 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Is there any status on this? rejected ? still under review ? DRH swamped. But it is on the list of potential changes for the Fossil Code Sprint in Munich on July 3! regards, Bapt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Thu, May 24, 2012 at 1:51 AM, Natacha Porté nata...@instinctive.eu wrote: If you don't mind, I'd rather have it not named at all. Due to how it's (still) heavily loaded with negative emotions, I would like not having to interact with the original project or its repository. And a name change at this level does involve quite a lot of interaction. In the open source community, people frequently start forks of other projects and develop them independantly under new names. A recent example of a high profile project is LibreOffice, which is a fork of OpenOffice. Thank you for your good work. And sorry that you got caught up in this controversy. You are in good company. History has many people who created great works that had unfortunate names. (I decline to name any as that is potentially another debate.) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 30, 2012 at 1:24 PM, Ron Wilson ronw.m...@gmail.com wrote: On Thu, May 24, 2012 at 1:51 AM, Natacha Porté nata...@instinctive.eu wrote: If you don't mind, I'd rather have it not named at all. Due to how it's (still) heavily loaded with negative emotions, I would like not having to interact with the original project or its repository. And a name change at this level does involve quite a lot of interaction. In the open source community, people frequently start forks of other projects and develop them independantly under new names. A recent example of a high profile project is LibreOffice, which is a fork of OpenOffice. Thank you for your good work. And sorry that you got caught up in this controversy. You are in good company. History has many people who created great works that had unfortunate names. (I decline to name any as that is potentially another debate.) I also would like to thank Natacha for her great contribution and hope that as time goes by she might revisit her relationship with the original project. Unfortunately, human reaction to certain things like project naming could be unpredictable and sometimes destructive. Hopefully all the involved can get over it. --Leo-- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
Hello, on Wednesday 23 May 2012 at 15:26, Richard Hipp wrote: Nevertheless, though attached by fraud, the name is still inappropriate, and must be changed before being added to Fossil. Thanks to some invaluable help, I finally managed to get it done (I think). My markdown C library shall henceforth be known as libsoldout. Name chosen in the same theme as markdown and discount, as one of the possible aims (and the one I know best of) of real-life markdowns and discounts, to make room for the new collection. The new repository is available at http://fossil.instinctive.eu/libsoldout/home and unless I misconfigured something, old links should be automatically redirecting to valid equivalents in the new repository. As far as I know, all the unfortunate references have been purged from the code. If there is any traces still lingering, please inform me and I will deal with them as promptly as I can. I have not changed anything in the proposed integration into fossil ( http://fossil.instinctive.eu/fossil-scm/timeline?r=markdown ) since there was no reference whatsoever to the original project in the first place. Known traces still lingering are: + the history of the project, but I'm strongly against rewriting history in general, and I don't believe this case is extreme enough to warrant a breach in the principle; + the static archives of v1.1 of the library, linked from http://fossil.instinctive.eu/ which will be replaced when I release v1.2 (which has just entered beta), probably in one or two weeks; + the reference to a fork in the home page, but since the it's the name of the fork I have no control upon it. That fork should probably not be mentioned at all, it will be removed in the next overhaul of the page, leaving only a reference to sundown, probably within a few weeks too. I there anything else I should do? Thanks for your attention, Natacha Porté pgpYHrEpDb7eo.pgp Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On 05/30/2012 02:28 PM, Natacha Porté wrote: Hello, on Wednesday 23 May 2012 at 15:26, Richard Hipp wrote: Nevertheless, though attached by fraud, the name is still inappropriate, and must be changed before being added to Fossil. Thanks to some invaluable help, I finally managed to get it done (I think). My markdown C library shall henceforth be known as libsoldout. Name chosen in the same theme as markdown and discount, as one of the possible aims (and the one I know best of) of real-life markdowns and discounts, to make room for the new collection. Hey Natacha, Thanks so much for leading the fork of this project! I followed, with some dismay, the news when the whole project name thing blew up a few years ago. I hoped someone would just do the right thing (i.e. forking it, what you've done now) to put that kind of unpleasantness in its place. So I'm happy to see it's finally been done. Now, if only someone would do the same with the GIMP..;) Steve The new repository is available at http://fossil.instinctive.eu/libsoldout/home and unless I misconfigured something, old links should be automatically redirecting to valid equivalents in the new repository. As far as I know, all the unfortunate references have been purged from the code. If there is any traces still lingering, please inform me and I will deal with them as promptly as I can. I have not changed anything in the proposed integration into fossil ( http://fossil.instinctive.eu/fossil-scm/timeline?r=markdown ) since there was no reference whatsoever to the original project in the first place. Known traces still lingering are: + the history of the project, but I'm strongly against rewriting history in general, and I don't believe this case is extreme enough to warrant a breach in the principle; + the static archives of v1.1 of the library, linked from http://fossil.instinctive.eu/ which will be replaced when I release v1.2 (which has just entered beta), probably in one or two weeks; + the reference to a fork in the home page, but since the it's the name of the fork I have no control upon it. That fork should probably not be mentioned at all, it will be removed in the next overhaul of the page, leaving only a reference to sundown, probably within a few weeks too. I there anything else I should do? Thanks for your attention, Natacha Porté ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Markdown engine integrated into fossil
Hello, stuff happens, and it turns out that now I have finished integrating my markdown library (libupskirt) into fossil. And I really mean integrating, that is using struct Blob as dynamic buffers and other idioms. I used it to translate *.mkd and *.markdown embedded docs in a similar way as *.wiki are currently translated. The end result is available in the markdown branch at http://fossil.instinctive.eu/fossil-scm/doc/trunk/www/index.wiki A demo repository using that extended fossil, with texts provided by bapt, can be found at: http://fossil.instinctive.eu/markdown-examples/doc/tip/README.mkd http://fossil.instinctive.eu/markdown-examples/doc/tip/FAQ.mkd As far as I can tell through visual inspection, the markdown engine passes the official markdown test suite. I don't publish the result becasue I haven't found any licence for the test suite, so I guess redistributing it is illegal. The current implementation supports only vanilla markdown along with talbe (using PHP-Markdown-Extra syntax). Quite a few other extensions can be easily added, just like they were in libupskirt, and I'm willing to add them (or remove the table extension) if a consensus can be reached on a particular set of extensions. I would gladly welcome any bug report, code review or otherwise constructive criticism. Hoping this helps, Natacha Porté pgpvys3FUuzZZ.pgp Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 5:53 PM, Natacha Porté nata...@instinctive.euwrote: I used it to translate *.mkd and *.markdown embedded docs in a similar way as *.wiki are currently translated. FWIW (not that my opinion really matters)... The addition of a more common wiki parser into fossil has arguably been the most-requested feature the past 4+ years i've been hanging around on this list. Everyone has their favourite/least favourite wiki format, but it seems to me (based largely on the many threads on this topic) that Markdown is the best-liked of the wiki formats (at least amongst the hacking community). While i don't personally care for markdown's syntax, i'd be all for seeing this make its way into the trunk just so we can finally move past The Wiki Wars ;). Happy Hacking! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 11:53 AM, Natacha Porté nata...@instinctive.euwrote: Hello, stuff happens, and it turns out that now I have finished integrating my markdown library (libupskirt) into fossil. We appreciate your efforts on behalf of Fossil. However, let me be very clear that any library with the name libupskirt has *zero* chance of ever getting official support or recognition from the Fossil project. Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it will be difficult to rehabilitate the code. Note that after reading this far, and observing our choice of library names, I have chosen to read no further in your post. And I really mean integrating, that is using struct Blob as dynamic buffers and other idioms. I used it to translate *.mkd and *.markdown embedded docs in a similar way as *.wiki are currently translated. The end result is available in the markdown branch at http://fossil.instinctive.eu/fossil-scm/doc/trunk/www/index.wiki A demo repository using that extended fossil, with texts provided by bapt, can be found at: http://fossil.instinctive.eu/markdown-examples/doc/tip/README.mkd http://fossil.instinctive.eu/markdown-examples/doc/tip/FAQ.mkd As far as I can tell through visual inspection, the markdown engine passes the official markdown test suite. I don't publish the result becasue I haven't found any licence for the test suite, so I guess redistributing it is illegal. The current implementation supports only vanilla markdown along with talbe (using PHP-Markdown-Extra syntax). Quite a few other extensions can be easily added, just like they were in libupskirt, and I'm willing to add them (or remove the table extension) if a consensus can be reached on a particular set of extensions. I would gladly welcome any bug report, code review or otherwise constructive criticism. Hoping this helps, Natacha Porté ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
on Wednesday 23 May 2012 at 12:18, Richard Hipp wrote: Note that after reading this far, and observing our choice of library names, I have chosen to read no further in your post. Oblivion was such a nice place for me to be... All by apologies for having dared creep out it. pgp2vbVQ9SlGI.pgp Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 06:28:59PM +0200, Natacha Porté wrote: on Wednesday 23 May 2012 at 12:18, Richard Hipp wrote: Note that after reading this far, and observing our choice of library names, I have chosen to read no further in your post. Oblivion was such a nice place for me to be... All by apologies for having dared creep out it. Natacha, thank you a lot for your work on fossil + markdown (and thank you for libupskirt). I also hold a modified version of fossil in a branch, where my changes did not please Richard; well, fossil is Richard's project, and it's up to him whether to accept some turns or others. And we can either keep a fork published or convince him to accept the changes; each option requires some work, and we have to balance. :) Richard, I hope you don't mind having the markdown code in a branch in the central repository. What do you think? On the other hand, I just looked for 'upskirt' on the dictionary and I had no idea on what it means. Maybe English people understand it just fine. But as someone already said in this thread, the libupskirt name does not appear in the fossil branch. Regards, Lluís. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 12:25 PM, BohwaZ boh...@bohwaz.net wrote: Le Wed, 23 May 2012 12:18:52 -0400, Richard Hipp d...@sqlite.org a écrit : We appreciate your efforts on behalf of Fossil. However, let me be very clear that any library with the name libupskirt has *zero* chance of ever getting official support or recognition from the Fossil project. Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it will be difficult to rehabilitate the code. Note that after reading this far, and observing our choice of library names, I have chosen to read no further in your post. Did you even check her branch? There is no mention of libupskirt in the code so far, so why the trolling on something irrelevant? Our goal is to create *beautiful* code. And there is nothing beautiful about voyeurism. Nor, I should add, is there anything beautiful about gratuitous profanity. Therefore, please mind your language on this list. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote: Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it will be difficult to rehabilitate the code. Do you mind explaining this bit please, Richard? TIA, -Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 12:36 PM, Weber, Martin S martin.we...@nist.govwrote: On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote: Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it will be difficult to rehabilitate the code. Do you mind explaining this bit please, Richard? https://www.google.com/search?q=upskirt http://en.wikipedia.org/wiki/Upskirt TIA, -Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On 2012-05-23 12:39 , Richard Hipp d...@sqlite.org wrote: On Wed, May 23, 2012 at 12:36 PM, Weber, Martin S martin.we...@nist.gov wrote: On 2012-05-23 12:18 , Richard Hipp d...@sqlite.org wrote: Furthermore, even if you rename libupskirt to something that is completely benign and inoffensive, it will be difficult to rehabilitate the code. Do you mind explaining this bit please, Richard? https://www.google.com/search?q=upskirt http://en.wikipedia.org/wiki/Upskirt Not that bit. The bit about even if you rename it to something that is completely inoffensive, it will be difficult to rehabilitate the code. Why is that? TIA, -Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 12:41 PM, Weber, Martin S martin.we...@nist.govwrote: Not that bit. The bit about even if you rename it to something that is completely inoffensive, it will be difficult to rehabilitate the code. Why is that? The choice of library name suggests that the author does not have a keen eye for beauty, in which case the code is unlikely to be something I would care to work with. Furthermore, I am disinclined to look at the code for fear of running across comments that I would prefer not to read. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 6:39 PM, Richard Hipp d...@sqlite.org wrote: https://www.google.com/search?q=upskirt http://en.wikipedia.org/wiki/Upskirt FWIW, and in Natacha's defense: i'm a native US-English speaker, but i've been away from the States long enough (going on 15 years) that the U word entered my vocabulary for the first time today. It cannot be expected that non-native speakers are always up-to-date on English slang. i vaguely remember Fossil's db file extension being changed from .fos to something else at one point because fos is a non-polite word in Polish (IIRC). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 1:00 PM, Stephan Beal sgb...@googlemail.com wrote: FWIW, and in Natacha's defense: i'm a native US-English speaker, but i've been away from the States long enough (going on 15 years) that the U word entered my vocabulary for the first time today. It cannot be expected that non-native speakers are always up-to-date on English slang. My apologies if your conjecture is true, and the use of the term upskirt in the library name was innocent. Yet, while I am open to evidence to the contrary, I suspect that in this case the word was used with full knowledge of its connotations. But, maybe we could move past this and focus on technical matters? (And on creating *beautiful* software.) i vaguely remember Fossil's db file extension being changed from .fos to something else at one point because fos is a non-polite word in Polish (IIRC). The filename was changed .fslckout to avoid the word for a kind of body waste (the exact nature of which is still unknown to me) in Hungarian. The old name is still supported for legacy but is undocumented and deprecated. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
The choice of library name suggests that the author does not have a keen eye for beauty, in which case the code is unlikely to be something I would care to work with. Maybe the name of the library just don't represent the same for the author as for you, different culture, etc; but this really have nothing to do with having a keen eye for beauty. Furthermore, I am disinclined to look at the code for fear of running across comments that I would prefer not to read. You should really have a look at the code, it was written far before the name of the library, and there are no comments of any kind like you seem to imagine. This is to bad that this great library is just pushed out because of an unfortunate name which was chosen for a joke (with references, that apparently noone from the native english speaking world get) and with out any perverse references in mind. Please have a look at the code before judging of anything about the author, just judge the code and work she has done. You don't even have to name the library on the commit log, just New markdown format support for embedded documentation or something like that. And if the name is a problem, I'm pretty sure she could easily be convinced to change the name of the library if someone come with a better name. Nothing in the code itself reference libupskirt regards, Bapt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
On Wed, May 23, 2012 at 1:31 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: This is to bad that this great library is just pushed out because of an unfortunate name which was chosen for a joke (with references, that apparently noone from the native english speaking world get) and with out any perverse references in mind. I was initially dubious of this claim, due to fluent style of the author Natasha writing. But further investigation, and references sent privately to me by other on this list (thank you) suggest that I was wrong, and that Natasha is in fact an innocent victim of fraud and that the name was actually selected by mischievous (dare I say perverted) third-party native English-speaking male. Therefore, I hereby publicly apologize to Natasha for accusing her of generating code that is less than beautiful, based solely on the name of the code. The code is once again a candidate for incorporation into Fossil. Nevertheless, though attached by fraud, the name is still inappropriate, and must be changed before being added to Fossil. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Markdown engine integrated into fossil
on Wednesday 23 May 2012 at 15:26, Richard Hipp wrote: Therefore, I hereby publicly apologize to Natasha for accusing her of generating code that is less than beautiful, based solely on the name of the code. The code is once again a candidate for incorporation into Fossil. Thanks. At this point I would like to say apologies accepted, but I do not want it to sound like a reference to Star Wars, because I do mean it literally. Nevertheless, though attached by fraud, the name is still inappropriate, and must be changed before being added to Fossil. If you don't mind, I'd rather have it not named at all. Due to how it's (still) heavily loaded with negative emotions, I would like not having to interact with the original project or its repository. And a name change at this level does involve quite a lot of interaction. However the code I wrote for fossil is significantly different from the original, due to the integration of fossil idioms (and I'm willing to integrate even more, but further idioms would have to be pointed out to me since I couldn't find them by myself). By the way, you might not like the formatting of the C code, and that too I'm willing to change upon request. I thought it would be dishonest concealment to not mention even once the name of the original project, since that's where part of the code and all the design comes from. But I mentioned it only once. Just like the subject of this thread, the code only talks about a markdown engine, without a name. Would the integration of such code, exactly like it is currently on my fossil clone, without any other reference to the original project than the first post of this thread, be acceptable? If it is not (for example if you really want references to the original project), then I'd rather we first address all technical issues, to ensure the code itself really has technical merit to be added, before proceeding to the painful renaming. Natacha Porté pgpdu022N7F8a.pgp Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
