Hi Since 2.14 it has not been possible to georeferencing an image. There are a bugreport on the issue http://hub.qgis.org/issues/14551 with a priority: Blocker. There is a comment • Target version changed from Version 2.14 to Version 2.16 What does that mean? Regards
Lene Fischer Associate Professor Department of Geosciences and Natural Resource Management University of Copenhagen MOB +45 40115084 [email protected]<mailto:[email protected]> [cid:[email protected]] Fra: Qgis-developer [mailto:[email protected]] På vegne af Tim Sutton Sendt: 18. maj 2016 20:55 Til: Junior Delaz Cc: qgis-community; QGIS Developer Mailing List Emne: Re: [Qgis-developer] [Qgis-community-team] Moving the install instructions to a more sexy, visible, coherent and translatable page in qgis.org Hi On 18 May 2016, at 12:49, DelazJ <[email protected]<mailto:[email protected]>> wrote: Hi, 2016-05-18 8:24 GMT+02:00 Tim Sutton <[email protected]<mailto:[email protected]>>: Hi After rereading the thread I think I am +1 for moving to RST in the QGIS Docs repo with the following thinking: Is the Doc repo a better candidate for this (if we get the go!) than QGIS website? Sorry yes, you are correct, the Web site is the better place. Regards Tim * QGIS Website is always translatable, so can easily show the most recent procedure in different languages. It also provides a chapter on development steps, might be worth having this beside. * Using website, we have a unique hyperlink (to use in our communication if needed) instead of having to update it after each released doc * testing doc (which in the ideal world, is related to master) is not to be translated * not all QGIS versions are/will be documented: the last doc provided is 2.8. The next should be 2.14 (btw, still looking for volunteers to write it - around 80 issues remaining and not the least) but when will be the release? * all the good stuff Junior mentioned like translatability, visibility etc. * when we hit release freeze we could copy the latest output from sphinx (maybe generated as plain text file?) to INSTALL.txt and remove the sources for the install docs from the QGIS code tree. That way the QGIS sources always contain the current notes for that release and the doc sources contain only the most recent procedure. * we could add a note in the docs sources saying ‘these instructions are for the current state of the develop branch only, for version specific install procedures, please see the INSTALL.txt in the source tree for that release’ +1 though the copy would be from the website repo (as suggested above) I think that workflow is not too much different from the current system. Of course someone needs to volunteer to get all the processes above into place :-P I'd RSTed the install doc and opened a pull request at https://github.com/qgis/QGIS-Website/pull/343/files. Might need correction. It's the content on April 15th. Don't however know the steps to keep this up to date nor automate some changes (like date of doc). Regards, Harrissou 2016-05-18 8:49 GMT+02:00 Jürgen E. <[email protected]<mailto:[email protected]>>: Hi Tim, On Wed, 18. May 2016 at 08:24:05 +0200, Tim Sutton wrote: > @Jürgen regarding your comments below, I used to use apt-get build-dep too > but I actually like the explicit package list your script generates more in > some ways because it is deterministic compared to build-dep which will only > reflect the deps from the current latest package in apt sources. The dependencies of the latest automatic nightly are probably more up-to-date than the list from the latest manual INSTALL update run. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<tel:%2B49-4931-918175-31> Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50<tel:%2B49-4931-918175-50> Software Engineer D-26506 Norden http://www.norbit.de<http://www.norbit.de/> QGIS release manager (PSC) Germany IRC: jef on FreeNode _______________________________________________ Qgis-community-team mailing list for organizing community resources such as documentation, translation etc.. [email protected]<mailto:[email protected]> http://lists.osgeo.org/mailman/listinfo/qgis-community-team _______________________________________________ Qgis-developer mailing list [email protected]<mailto:[email protected]> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer [cid:[email protected]] --- Tim Sutton QGIS Project Steering Committee Chair [email protected]<mailto:[email protected]>
_______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
