> > Multiline descriptions in the metadata are allowed, newlines are not > converted to BR in the HTML though...
Good to know ! Is it ok to use HTML then ? Does the same apply to the changelog ? ... The default metadata.txt file should be more explicit about how to format the entries... A few days ago I added an "&" in the author fields (since we were two authors), and the plugin wasn't downloadable anymore (it uploaded well though). 2014-02-12 13:32 GMT+01:00 Alessandro Pasotti <apaso...@gmail.com>: > 2014-02-12 13:20 GMT+01:00 Olivier Dalang <olivier.dal...@gmail.com>: > > Hi ! >> >> -1 for making the homepage mandatory... >> If it's only to display the plugin's help/readme information, we should >> rather have the developpers create some help/readme file for each plugin, >> which could be opened directly from within QGIS. >> IMO that's much better than a link which opens in the browser, and which >> most of the time will be either irrelevant (since no one will spend time to >> make a homepage for a plugin), or a quite technical looking github readme >> page, which precisely displays a readme.md/txt/html page. >> >> +1 for the tracker and the repository ! >> >> On the same topic : >> >> I find the descriptions of the plugins often too synthetic to really know >> what a plugin is good for. >> >> I'd say this comes from the fact that descriptions can be on one line >> long in the metadata file. >> >> Having the ability to use multiple lines would be much better, and we'd >> simply show the first line only in compact views (listings...). >> >> > > Multiline descriptions in the metadata are allowed, newlines are not > converted to BR in the HTML though... > > > -- > w3: www.itopen.it >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer