On Jul 19, 2013, at 6:09 PM, Alain Busser <alain.bus...@gmail.com> wrote:

> That's great, even faster than bioPython, and thanks to Petit Parser. That's 
> great!
> 
> I hope it will be on good place on Pharo's web site...
> 
I will add it to the publication lists and make a news entry...


> 
> On Wed, Jul 17, 2013 at 11:14 PM, Hernán Morales Durand 
> <hernan.mora...@gmail.com> wrote:
> Hi Marcus,
> 
> Thank you for the comments, I have been checking the link distribution 
> conditions and they say people can access the article only from the Oxford 
> Journals website for academic purposes, so here it is:
> 
> http://bioinformatics.oxfordjournals.org/content/early/2013/07/09/bioinformatics.btt398.full.pdf?keytype=ref&ijkey=Y2j8jNeEKVNl0rD
> 
> Sorry for the inconvenience.
> Cheers,
> 
> Hernán
> 
> 
> 
> 2013/7/17 Marcus Denker <marcus.den...@inria.fr>
> 
> On Jul 16, 2013, at 9:31 PM, Hernán Morales Durand <hernan.mora...@gmail.com> 
> wrote:
> 
> > Doru, I can access the article through the "Full Text (PDF)" link at the 
> > right box titled "This Article". Maybe you have the right columns 
> > collapsed? There is an arrow button "Show all columns" if you cannot see 
> > the link.
> > Let me know.
> >
> 
> Publishing is the act of making Paper in-accessible to the Public (that's 
> where the name comes from).
> 
> So what all serious publishers allow you to do is to make the version that 
> you send them (not their version) available from your
> website and/or an online-archive of your employer,
> 
> It is very important to do that, as people will not jump through hoops to get 
> your paper (e.g. go to the library?).
> In the past I send emails to authors to get paper copies, but today I would 
> just *never* do that. If *you* don't make your
> paper available, why should I bother? i will just not read it and not cite it.
> 
> The journal publishing is just important for your CV and getting tenure and 
> things like that, the paper the people
> really *read* is the one they can download from your website.
> 
>         Marcus
> 
> 

Reply via email to