> > On 03/11/2012 11:55 AM, Martin Dobias wrote: > >> Anyway it's worth noting that when rendering text there are two > possibilities: > >> 1. draw text (old labeling) - faster, hard to draw buffers (currently > >> being drawn by shifting the text several times) 2. convert text to > >> vector path + draw path (new labeling) - slower, but with nice > >> buffers (antialiased etc). Problems: text is converted to vectors -> > >> harder postprocessing, bigger buffers are not drawn correctly. > >> > >> Martin > > > > Ah, that explains why the text isn't exported as text in svg files. > > Would it be possible or make sense to do both. E.g. the text stays > > text but a copy is converted and buffers are generated on the copy > > that is a path? > > I haven't tried that but I expect that it will not look good because the > rendering algorithms are different. > > I will be probably moving new labeling to use directly text drawing in > future since path drawing is several times slower... > > Martin
For what it's worth - the PDFs I've seen produced by ArcGIS and Mapinfo do have the text as text and the buffer as a path, but the buffer is quite simplified, at least for small text (and it can look quite bad). Alister _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
