RE:[Inkscape-user] HELP ! no text in IE6 (Feature Request)
Hi Julio, I think the problem is to do with the text, did you convert it to a path object before you viewed it in IE? I think that you have to do this in order to get it to display in Adobe Viewer plugin. I think this problem also occurs in KDE's Konqueror browser.
On that subject, I want to make a feature request. A way to convert a path (that was originally text) back to text.
The logistics of it would be that when you make the conversion to path, the text data is saved in the svg document, as well as all the transformations to the path after it's converted. Then, with the path-to-text feature, you encode the path back into text, including the transformations (colour, size) and are then able to edit in the text editor.
Regards,
Paul Jensen
The problems probably that 0.42 is creating flowtexts which arent yet supported by adobe, theres an option on the text menu to convert to standard text objects, which should work, while retaining editabiliy. Havent got Inkscape handy atm so cant look to see what the exact name of the command is.
Cheers
John
--- Paul Jensen <paul.jensen@...418...> wrote:
Hi Julio, I think the problem is to do with the text, did you convert it to a path object before you viewed it in IE? I think that you have to do this in order to get it to display in Adobe Viewer plugin. I think this problem also occurs in KDE's Konqueror browser.
On that subject, I want to make a feature request. A way to convert a path (that was originally text) back to text.
The logistics of it would be that when you make the conversion to path, the text data is saved in the svg document, as well as all the transformations to the path after it's converted. Then, with the path-to-text feature, you encode the path back into text, including the transformations (colour, size) and are then able to edit in the text editor.
Regards,
Paul Jensen
SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
On Sun, 7 Aug 2005, Paul Jensen wrote:
Date: Sun, 07 Aug 2005 09:37:47 +0100 From: Paul Jensen <paul.jensen@...418...> Reply-To: inkscape-user@lists.sourceforge.net To: jumiro@...956..., inkscape-user@lists.sourceforge.net Subject: RE:[Inkscape-user] HELP ! no text in IE6 (Feature Request)
Hi Julio, I think the problem is to do with the text, did you convert it to a path object before you viewed it in IE? I think that you have to do this in order to get it to display in Adobe Viewer plugin. I think this problem also occurs in KDE's Konqueror browser.
On that subject, I want to make a feature request. A way to convert a path (that was originally text) back to text.
What I do as a workaround is duplicate the text, hide it (visibility="hidden") and then convert the second version to a Path.
Sincerely
Alan Horkan http://advogato.org/person/AlanHorkan/
On Sun, Aug 07, 2005 at 09:37:47AM +0100, Paul Jensen wrote:
Hi Julio, I think the problem is to do with the text, did you convert it to a path object before you viewed it in IE? I think that you have to do this in order to get it to display in Adobe Viewer plugin. I think this problem also occurs in KDE's Konqueror browser.
On that subject, I want to make a feature request. A way to convert a path (that was originally text) back to text.
The logistics of it would be that when you make the conversion to path, the text data is saved in the svg document, as well as all the transformations to the path after it's converted. Then, with the path-to-text feature, you encode the path back into text, including the transformations (colour, size) and are then able to edit in the text editor.
Hi Paul,
Thanks, this is a good idea. I believe this has already been suggested as a feature request, but for future reference note that the official place for requests for feature enhancements (RFE) is via the website RFE tracker.
Your suggested approach matches up with ideas I've heard in the past for implementing this capability, so that's really good. You may want to think about what other information should be captured, such as the font face and size, etc.
If this is something you're passionate about, and if you understand C coding, I suspect this may not be too difficult of a feature to implement. If you'd like to give it a shot, I'd definitely encourage you to try. It'd be a very cool feature for the next release.
Bryce
On 8/13/05, Bryce Harrington <bryce@...69...> wrote:
On Sun, Aug 07, 2005 at 09:37:47AM +0100, Paul Jensen wrote:
On that subject, I want to make a feature request. A way to convert a path (that was originally text) back to text.
The logistics of it would be that when you make the conversion to path, the text data is saved in the svg document, as well as all the transformations to the path after it's converted. Then, with the path-to-text feature, you encode the path back into text, including the transformations (colour, size) and are then able to edit in the text editor.
This sounds extremely convoluted, and I'm afraid it will be very buggy, not to mention too much work for too little gain (unless I misunderstand your reasons). What I think we need instead is simply a checkbox "Convert all text to paths" when saving as Plain SVG, similar to what you get when you export EPS.
It's obviously up to the user to keep the original Inkscape SVG file with editable text and reexport it to plain if necessary. Trying to get both editability and text-in-paths precision _combined_ is not going to work reliably, IMHO. And even apart from that, it's really not necessary, because any such extension will work only in Inkscape anyway, other renderers won't benefit from it any more than from simple text-converted-to-path.
participants (5)
-
Alan Horkan -
Bryce Harrington -
bulia byak -
John Cliff -
Paul Jensen