The language of the Bulletin is English, but authors at their discretion may provide an exact translation of the Abstract in their native/local language. In the case of textual quotations, the inclusion of the quoted text in the original language, accompanied by a translation is preferred to the inclusion of the translation alone.
Guidelines for text
The text should be written clearly and concisely, using language that can be expected to be widely understood. Spelling should be thoroughly checked, and authors should have the text revised by a native speaker who is well-versed in academic writing so as to avoid delays in publication and/or rejection. In all cases, a semantic markup should be used instead of a visual markup: for example mark section headings as such, rather than using bold. Do not worry about how the text looks on your screen, just make sure that the logical order of heading levels is correct. Be aware that as typesetting is done by the editor, manuscripts will be returned to authors for editing if this requirement is not closely followed.
References, even if already included in the text, should also be submitted in a "database" format, preferably BibTeX, EndNote or RefMan, which are supported as an export format by most reference manager software. Bibliographic data must include DOI for articles and book chapters (and books if available) and ISBN for books. Be aware that many old articles have been retrospectively assigned DOIs. These retrospectively assigned DOIs can be found at the publishers web sites, like Springer Link, etc. They do not appear on the PDF files as they were not available at the time of printing, but instead they can be found in the page where the on-line abstract is displayed.
Acceptable file formats for body text: Submission of manuscripts should preferably be as Markdown, Rmarkdown, Rnw, LaTeX, open-doc, MS-Word (.docx), HTML, or plain text. In the case of Rmarkdown (.Rnw) files, all R packages used should be provided, for example using packrat. For final publication, illustrations should be supplied as separate files (see below), which can be linked, but should not be embedded in MS-word files. Those graphs which are provided as source code in LaTeX, Rmarkdown or Rnw files are exempt from this restriction: in this case make sure that you have included all data files needed. More information about how Markdown fits into the production of the final page output is available at http://kieranhealy.org/blog/archives/2014/01/23/plain-text/, but remember that we will take care of all steps after the writing of the .md markdown file. You need to submit only the .md file plus any illustrations to be included as separate files. A simple template is shown here
Guidelines for illustrations
Design of illustrations and sizing of their elements
Illustrations should be designed taking into account the text area for either single or double column inclussion in pages. All text and markings on illustrations should be present in the supplied files. Text on illustrations should use a san-serif font and the x-height should be at least 2.5 mm at the final published size. Colours should be chosen with care to ensure readability. The possibility of printing or photocopying in black and white, and discrimination of colours by readers with colour blindness, should be considered. For example, if using colours to indicate treatments, use an additional visual cue like symbol shape or line type to cater for these special cases.
Data plots: any designs that detract from visualization of data values are disallowed, including the use of 3D effects and shadows in bar plots. Pie charts are discouraged, as human beings are much worse at comparing angles than lengths, and allowed only with at most 5 slices per pie. Actual axes, or a box formed by the axes, and possible a grid when useful, are allowed. However, scatter plots, bar plots, histograms, and other plots should not the enclosed in extraneous additional boxes or use background colours or graying outside the plotting area. Axes should be labelled with the name of the displayed quantity followed by units enclosed in parentheses. Be aware that the scale and units should match the tick labels, i.e. even if logarithm based distances are used along an axis, if tick marks are given in the original units, "log" should not the mentioned in the axis label. Axis limits close to zero, but not quite at zero should be always extended to zero. It is preferible to use sparse tick labels along axes, in our view including more than five tick labels is in most cases of no help, or detrimental by making plots cluttered. One last point is toalways be careful when checking for possible overlap between figure elements which could hide observations or labels.
Accepted files formats
Illustrations embeded in PowerPoint, MS Word and similar application files are not acceptable unless accompanied by the same individual figures in separate files in one of the formats mentioned later in this section.
Vector graphics such as data plots, line diagrams, flowcharts, should not be submitted as bitmaps. Acceptable file formats for vector graphics: EPS (with embedded fonts), PDF (with embedded fonts), or svg. For online publication vector based formats yield smaller file size allow smooth re-scaling.
Illustrations like photographs, scanned handwriting or hand-drafted graphics are best submitted as high resolution bitmaps. Acceptable file formats for bitmaps are TIFF (16 bit or 8 bit), EPS, PDF, PSD (photoshop), png, jpeg (highest available quality for compression). If the original graphic fails to meet the desired resolution or quality, do not attempt to nominally fulfill the requirements, just submit the originals and they will be used at the size that their quality allows. Please, aim to submit bitmaps that have a resolution of 300 dpi to 600 (dots per inch) at the size the figure will be printed. For composite figures comprising several bitmaps, a single combined bitmap prepared by the authors should normally be submitted instead of several individual images. Of the compressed file formats use .png whenever the bitmap contains a discrete number of colours or shades of grey.
Every illustration should have a caption. In every data plot the units of expression should be clearly shown, and if error bars are included, it should be clearly explained what they represent.
Permissions for use of illustrations
Before publication authors should make sure that: 1) either they own the copyright, and that any earlier transfer of copyright to other parties, allows publication under the chosen CC licence for the article, 2) that for every photograph not taken in a public place, authorization in writing for publication has been obtained, 3) if the illustration is already publicly available under a compatible licence this should stated, and the original author named in the legend, 4) that any reuse of data has been explicitly authorized in writing or is allowed by the licence used in the original publication. Payment of any damage or costs, including all legal costs, incurred by the UV4Plants association caused by authorsâ€™ failure to comply with these requirements will be the full responsibility of the authors.
Authors, or their employers, will retain ownership of copyright. However, original publication in the Bulletin should be always cited upon republication in unaltered or altered form. The UV4Plants Bulletin contents will be published under one of the Creative Commons Licenses, by default CC BY-SA 4.0, but at the request of the authors, other more restrictive (CC BY-ND 4.0, CC BY-NC 4.0) or less restrictive (CC BY 4.0) licenses can be used for individual articles. https://creativecommons.org/
The names and email addresses entered in this journal site will be used exclusively for the stated purposes of this journal and will not be made available for any other purpose or to any other party. However, the present time these data are transmitted between server and client unencryted when entered or consulted.