Dirk Schulze
My feedback
43 results found
-
21 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Dirk Schulze
commented
Turn off "Responsive" option in the SVG Save as/Export as options and the width and height attributes will be added to the SVG file.
-
3 votes
An error occurred while saving the comment Dirk Schulze
commented
This indeed is a limitation with SVG export in Adobe Illustrator currently.
-
1 vote
An error occurred while saving the comment Dirk Schulze
commented
SVG unterstüzt keine inneren oder äußeren Konturlinien. Für die Korrekte Darstellung in SVG Viewern (z.B. im Browser) werden Konturlinien zu Pfaden umgewandelt.
-
3 votes
An error occurred while saving the comment Dirk Schulze
commented
I understand that the symbols exported to SVG via File/Save as/SVG are visually correct but the resulting SVG has transforms and viewBoxes in the markup that you'd like to avoid.
As a temporary workaround, please use File > Export > SVG (or Asset Export).
-
27 votes
I am glad to update that this issue was fixed in 23.0.5 release.
Thank you for all the feedback.
An error occurred while saving the comment Dirk Schulze
commented
@Pierre I am sorry that you still experience issues where <textPath> doesn't get imported visually correctly for you. There isn't anything specific that you'd need to do on import. It should just work.
Do you have an SVG file that you can share with us? Just change the extension from .svg to .txt and upload it here. We would like to take a look at it and see if we can find the issue.
Thanks a lot for your patience,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hello from Illustrator. Thanks a lot for reporting this issue. We are targeting the issue in multiple iterations.
Starting with Adobe Illustrator 23.0.6, SVG files with <textPath> (text-on-path) get imported visually correctly. This means, all characters get positioned and rotated along a path as specified by SVG 1.1.
We are working on importing text-on-path semantically correctly as well so that in future iterations of Adobe Illustrator text can get edited more easily on the path directly.
We hope that the first iteration will solve a lot of issues that you are facing today and ensure that we are improving SVG import constantly.
Thanks,
Dirk -
3 votes
An error occurred while saving the comment Dirk Schulze
commented
Hi Kris,
Dirk from Adobe Illustrator here. We are very sorry for the issue you experience. Could you try the following please?
1. Open the SVG file in question in a text editor.
2. Save the SVG file to a new SVG file with a different file name.
3. Open the new SVG file in Adobe Illustrator.Please tell us if the newly created SVG file opens in Adobe Illustrator.
Thanks,
Dirk -
4 votes
An error occurred while saving the comment Dirk Schulze
commented
For testing
An error occurred while saving the comment Dirk Schulze
commented
Just as an update:
We contacted the support team at UserVoice and they said that they will add SVG and Ai file upload support shortly.
In the meantime it should be possible to change the extension of SVG files to .txt
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Brennan,
I fully agree! However, I haven't figured out if we are even able to change this and allow SVG files or compressed files as attachments. At this point, the only alternative is using a file sharing host.
I'll keep you posted when we find alternatives,
Dirk -
38 votesUnder Review · 16 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment Dirk Schulze
commented
Hi Brennan and Francis,
@Brennan We will review the issue with character and paragraph styles.
@Francis Got your request to multiple classes applied to an element. We will review it as soon as possible. It is a tricky one though. As mentioned by @Brennan, we are half way there if you use “Graphic Styles”.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Gregan,
Thanks a lot for opening this feature request! Could you please send the minimal Ai test file (the one with the .a, .TWO, .b output) to sharewithai@adobe.com?
Do I understand your request correctly that you want to give each style class an individual name or do you want to have them all the same individual prefix?
Also, would creating and applying graphic styles with names of your choice be suitable for you if the same name is chosen as CSS class name on the SVG export?
Thanks a lot in advance,
Dirk -
10 votesUnder Review · 8 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment Dirk Schulze
commented
Hello LNMB,
Thanks a lot for confirming the intend. We are currently reviewing the request and will add it to our backlog.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Thomas, Tamer and LNMB,
Thanks a lot for your reply to this issue. We have a couple of more questions to your request.
@Tamer @LNMB Adobe Illustrator already does have the option to convert all text of a selection/artboard/document to outlines for SVG export. You may find the option in the Font dropdown menu. Select Convert To Outlines in the SVG Export dialog. The text in your original document will not be affected by this option and stays text.
If you use Assert Export, use the settings icon (a cog), go to the SVG tab and you'll find the setting there as well. If you are aware of the SVG Export dialog but didn't see the option to convert to outlines, please let us know how we can make the option more visible.@Thomas I'd like to understand the issue with the text looking thicker on export. The current result of converting text to outlines is the same as selecting the text object and going to the menu item Object > Expand... Are you comparing the expansion result with the original text? Text engines have some additional techniques like hinting that try to avoid aliasing. Without that, expanded results may indeed look thicker or less crisp on edges than the original text. The results also depend on screen resolution and platform and might be quite noticeable.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hello Stephen,
Thanks a lot for reporting your experience with the Export as dialog for SVG export. We are currently reviewing your request.
Greetings,
Dirk -
4 votes
Hi Akshay,
We were able to confirm the issue that you see. The issue indeed does not happen with Illustrator 2018 (22.1).
We identified hyphenation as the potential culprit. To workaround the issue, either disable hyphenation in the Paragraph panel or make sure text does not get hyphenated.
We are sorry that you experience the issue and are working on fixing the issue.
The Adobe Illustrator Team
An error occurred while saving the comment Dirk Schulze
commented
Hi Akshay,
Thanks a lot for sending the file to us. We are currently reviewing the issue and will open a backlog item.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Akshay,
Thanks a lot for reporting this issue. One way to share Illustrator files with us is by sending an email to sharewithai at adobe dot com.
Illustrator, currently, flattens text if it includes surrogates or emojis. Could that be the issue you see?
Greetings,
Dirk -
1 vote
An error occurred while saving the comment Dirk Schulze
commented
Hi Shahar,
Uploading Ai files or ZIP files doesn’t work with UserVoice yet. Would it be possible for you to send an Ai file to sharewithai (at) adobe dot com?
Thanks a lot,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Shahar,
I am very sorry that you see this issue. Would it be possible for you to share the Ai file with us? You may zip it and upload it here.
Thanks,
Dirk -
14 votes
An error occurred while saving the comment Dirk Schulze
commented
Thanks a lot for the information. We put the matter under review and will add it to our backlog afterwards.
An error occurred while saving the comment Dirk Schulze
commented
Hi from Adobe,
At this point, the only way to get the <?xml version="1.0" encoding="utf-8"?> element from Illustrator is to use the File > Save as option. We are considering an option to export with the encoding tag in the future.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hello Taylor,
I am not sure I understand your issue. Export As does leave <?xml version="1.0" encoding="UTF-8" ?> out on purpose. Especially web browser don't need this tag anymore and some browsers like IE 9 don't even support the SVGs with encoding tag. The majority of SVG viewers beside web browsers don't require this tag either.
Could you provide an example file that would not work w/o the encoding tag?Thanks a lot,
Dirk -
5 votes
An error occurred while saving the comment Dirk Schulze
commented
Thanks a lot for sharing the SVG file with us. We will review the issue ASAP and get back to you.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hello Devra,
I am really sorry to hear that you have issues with opening the SVG file in Illustrator. Would it be possible to share the file in question with us? It would be great if you could either upload the SVG file here (maybe with .txt extension so that UserVoice accepts the file) or mail it to sharewithai (at) adobe dot com.
Thanks a lot for reporting the issue,
Dirk -
5 votesUnder Review · 8 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment Dirk Schulze
commented
Hi Friedrich,
Thanks a lot for your feedback. We definitely have the 2nd workflow and especially the most-minimal-destructive preservation part on our long term roadmap. And we will consider keeping the document structure, author data, meta data and styling information as untouched as possible. (A truly round-tripping experience.) This may take us some more time though.
If there is any low hanging fruit that we can do in the short term that would have an immediate impact to your workflow we would be very interested in that.
I wonder what benefits you see with workflow 1, the pure import workflow. What information would you like us to keep? How is it different from workflow 2?
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hello Benjamin,
I share your frustration and we are constantly improving the import of SVG into Illustrator.
A question to you: As mentioned, InkScape preserves its own primitives in the SVG file while providing a fallback for non-InkScape viewers and authoring tools. What would be your expectation to Illustrator when you modify an element that has InkScape primitives that might no longer be valid with the changes from Illustrator? Should Illustrator remove those annotations actively? What if the annotations from InkScape are still valid even with the change from Illustrator? Is it still ok to remove the annotations/primitives?
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Benjamin,
I understand the issue that you are facing and I understand the request to support "a simple round-trip" experience for SVG.
However, there are a lot of things to consider:
* SVG has a very limited set of features considering the complexity of most illustration applications even beyond Adobe Illustrator. Every authoring tool has a different way to handle the limitations.
* InkScape uses its own namespace to enrich SVG documents with the features that go beyond the capabilities of InkScape and provides a fallback for SVG compatible implementations.
* Illustrator, as any other SVG consuming application but InkScape itself, is only able to understand the SVG compatible fallback.Even if Illustrator would try to keep more metadata from the originally imported SVG document and you do edits to the SVG document in Illustrator, those would not play nicely with InkScape since Illustrator would really only modify the fallback but not InkScapes enhancements.
As said, InkScape enriches the SVG document with its own capabilities. However, this really just makes the SVG document an InkScape specific file format like Illustrator's own .ai file format. Since the feature set of both applications are very different, a fulfilling round-trip experience won't be possible.
Just like InkScape, you can preserve Illustrator's capabilities in SVG as well and Illustrator provides a fallback rendering for all SVG compatible implementations. InkScape runs into the same issue when opening such an SVG files from Illustrator as it is the other way around.
Therefore, Illustrator considers SVG more of an export format than a native file format. To clarify, this is not a reason of Illustrator being older than SVG but a way to handle the limitations of SVG.
I hope that clarifies the issue and explains why keeping more metadata on round-tripping wouldn't actually solve the issue you are facing.
Greetings,
Dirk -
149 votes
Just a general status update. We are currently and will continuously improve SVG import support in Adobe Illustrator. We are currently working on solving the issues mentioned in this report. Please feel free to open new bug reports here on uservoice if you are experiencing additional/untracked issues.
An error occurred while saving the comment Dirk Schulze
commented
Thanks a lot for the feedback Nick! We will review it and add it to our backlog.
An error occurred while saving the comment Dirk Schulze
commented
Hi Nick,
If we provide the option to scale the content to 96ppi, would you be hostile to the idea to simply adjust the viewBox attribute to match the 96ppi from a CSS pixel?
As said, beside reopening an SVG file into Ai, the main concern is about rounding fractions of horizontal or vertical dimension values like path segment coordinates, x, y, width, height and so on. If we adjust the viewBox, this issue would not rise.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
@LM @NickA is right that there is a difference between 72 ppi (CSS points) and 96 ppi (CSS pixels). It is not as easy to fix the issue as it seems at first though.
Illustrator treats both, pixels and points, as 72 ppi. Illustrator has been around for more than 30 years. Far longer than CSS which introduced this difference. There is a lot of content that either uses pixels or points as document/font units. We can not simply support 96 ppi pixels internally and one reason is the huge amount of existing .ai content.
At the same time we want to support SVG as good and as interoperable as possible. And here again, there is a lot of content that gets exported to SVG but never targets other applications or use cases than Illustrator. All documents that get saved/exported as SVG may get imported again. As a matter of fact, a lot of users want to import SVG documents back into Illustrator.
Should we support 96 ppi CSS pixels on export we may need to treat content (and CSS pixels) with 96 ppi on import as well and transform them to the 72 ppi Illustrator space. This introduces a couple of problems:
* Numbers get stripped on export and precision gets lost. This may be most noticable when 2 shapes get drawn right next to each other. Gaps might start appearing between the two space that haven't been there before. Or shapes start overlapping.
* We can not distinguish between previously generated SVG content that assumes 72 ppi and new content that assumes 96 ppi. Either the 96 ppi asuming content or the 72 ppi assuming content will get imported incorrectly.
* Transforming from 72 ppi to 96 ppi on export will create fractions on all length values (x, y, width, height, cx, rx, ...) and path segments. So 17pt get to 22.8959...px. Customers previously told us that this is not acceptable.
* Transforming from 72 ppi to 96 ppi on export and back to 72 ppi on import will not necessarily give the same values back after import because of rounding issues described above. Especially on text you will start noticing differences where text chunks are not aligned vertical correctly anymore or kerning betwen characters will start looking weird.At the end, SVG is a vector format and can get scaled into any bounding box. Since units in Illustrator are consistent within the document, the exported SVG file work as expected in web content. That is why the majority of web developers do not notice the difference today.
Please let me know if, despite the issues explained which will affect all application workflows as well (even Illustrator <-> InkScape), you would still be interested into exporting with SVG at 96 ppi for pixels.
If you have different proposals how to support 96 ppi CSS pixels not described above, let me know as well.
An error occurred while saving the comment Dirk Schulze
commented
Hi Monika, Martin, Francisco, Ruth, Alec and others,
I am answering to some of the comments below. In general, please open separate issues for individual issues you see in Adobe Illustrator. Even if they all are related to SVG.
@Monika The Adobe Illustrator 2019 release fixes the issue that you see with the linked SVG example. The one with the flag of the EU. There should no longer be warnings about maximum nesting levels and the layer tree should look much flatter than it used to. We also fixed a few issues with masks.
@Alec The Adobe Illustrator 2019 release has support for the fill-rule property of SVG. Your example should import correctly now. We still have some work to do with masks though we did fixes here as well. Gradient and pattern transforms should import in general though we will improve support even more in future releases.
@Rith and @Martin Adobe Illustrator does not draw strokes in the coordinate space of the object as defined by Postscript or SVG. This causes the difference between the stroke width that you see in Adobe Illustrator on import and other SVG viewers. We will continue to improve the import further in future releases.. In general, the rendering model differs which causes the visual differences at the moment.
@Francisco Adobe Illustrator does not support import of images in SVG of formats other than raster images. Neither for embedded images with dataURLs nor linked images.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hello Ruth,
Thanks a lot for your feedback Ruth! It would be great to hear more about the stroke-width issue that you run into. I tested this minimal example:
<svg xmlns="http://www.w3.org/2000/svg">
<rect x="10" y="10" width="100" height="100" style="stroke:black;fill:none;"/>
<rect x="120" y="10" width="100" height="100" style="stroke:black;fill:none;stroke-width:1"/>
<rect x="230" y="10" width="100" height="100" style="stroke:black;fill:none;stroke-width:1px"/>
<rect x="120" y="120" width="100" height="100" style="stroke:black;fill:none;stroke-width:10"/>
<rect x="230" y="120" width="100" height="100" style="stroke:black;fill:none;stroke-width:10px"/>
</svg>but all stroke-width values compute correctly after opening in Adobe Illustrator. Could you please post a short example here? Or, for bigger files, it is also possible to use sharewithai@adobe.com
Thanks a lot in advance!
Greetings,
DirkDirk
An error occurred while saving the comment Dirk Schulze
commented
Hi Monika. I can confirm the issues with nested <use>s. Illustrator (unnecessarily) creates too deeply nested groups. Eventually, it will reach the maximum allowed group nesting level and stops drawing. I logged that issue.
Illustrator does not use SVG as its native document format. Even though Illustrator does try to preserve certain attributes on SVG import it is not enough for a full SVG round tripping experience. Do you want to use Illustrator as "SVG editor" where structure, styling blocks and class names get preserved as much as possible, or is it enough to preserve attributes, styles and interactions on the element level? So CSS classes might get remixed as it makes sense for the exported SVG document.
What issues do you have with groups and masks?
Hi Alec, self referencing masks should not crash Illustrator in the latest release anymore. Nested masks, fill-rule are still an issue and I logged those. Could you share some failing examples with gradients, image transforms and patterns please? Please feel free to create separate user voice reports per SVG issue and file them as bugs. Thanks a lot!
-
11 votesNeed More Info · 11 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment Dirk Schulze
commented
Thanks Edu Couches for the detailed explanations! This indeed is really useful.
To point 1-3:
Same colors in the same class are offered by the File > Export as (Export For Screens.../Asset Export) work flows. I encourage you to try it and am eager to hear your feedback.It is possible to export pre-defined CSS classes with custom names by using Graphic Styles in your artwork (See Panel Graphic Styles). When you drag an element into the panel, a new graphic style will be created. You can name it and reuse it on other elements. The name of the graphic style will be used as CSS name. That should address the class issue you describe.
To 4:
We do have a CSS Extract/Export Option but that will likely not address the described issue. Will add that to our backlog.If you name a group, shape or text element, the File > Export as Route will use that as an ID. I hope this addresses the ID issue.
To 5:
I am not quite getting the ask. As you said, the Layer panel provides a hierarchical view of the Ai document structure. For SVG export we might clean it up a bit and remove the internally created groups but we are doing it ad hoc. What difference do you expect to the Layer panel?Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Ricardo,
The inactive SVG code... button definitely is a bug. It would be great if you could send us an Ai document where this bug appears to sharewithai@adobe.com. We are not able to reproduce this issue.
In the mean time, could you try using File > Export as (select SVG)? This should have a button called "Show Code" and also provides you access to the source code with out copy&paste into a text editor.
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Ricardo, this is very odd. This button should not be inactive. Does this issue happen with the latest release of Illustrator? Is there anything specific about the Illustrator document? Does it have huge amount of content? Many raster images or mesh gradients? Would it be possible for you to share an Illustrator document with the Illustrator team privately?
Greetings,
Dirk -
10 votes
An error occurred while saving the comment Dirk Schulze
commented
Hi Brennan,
With renaming you refer to class names when importing the SVG file back? (The round-tripping experience.) Or is there an issue even with saving the Graphic Styles and naming conventions?
Greetings,
DirkAn error occurred while saving the comment Dirk Schulze
commented
Hi Brennan,
Are you familiar with Graphic Styles in Illustrator? If you have a couple of shapes with the same styling, you can create a common "Graphic Style" for the shapes and reuse this styling pattern. This can be done in the "Graphic Style" panel (Window > Graphic Style).
Then try File > Save as and chose SVG (this may not work with one of the export options yet so try Save as for now). The common graphic styles should be exported as classes if you select "Style Element" as "CSS Properties" setting in the Advanced tab for SVG options.I am curious if that is one of the requests you were looking for.
Thanks in advance,
Dirk -
2 votes
An error occurred while saving the comment Dirk Schulze
commented
Hello Martin,
Thank you for reporting the issue that you see and excuse the delay of the response.
If I understand the screenshots correctly, with distortion you mean that the content gets scaled from one to the other version of Illustrator.
I would love to look at the SVG file. Would it be possible to share the file with us? You may either upload the SVG file here directly (maybe add the extension .txt to make UserVoice happy) or email it to us at sharewithai (at) adobe dot com.
Also, would it be possible to share the source of the SVG file? Was it created in Illustrator or a different tool?
Thanks in advance,
Dirk -
2 votes
An error occurred while saving the comment Dirk Schulze
commented
Hello Mark,
The intention nowadays is to use Export For Screens... (File > Export) or the Asset Export panel. Those export options provide much better and smaller results that are more suitable for web browsers and other modern SVG consumers.
I hope this helps.
Dirk
To the original post (File > Export As > SVG), make sure to select "Layer Names" in "Object IDs".
There was an issue in some Illustrator versions where the selection "Minify" did not respect the choice of "Object IDs". This has been fixed.
To:
> When I export an SVG, I choose "unique" for Object IDs. In the past, Illustrator would take my layer names and use them in a "data-name" attribute on the SVG tags.
This is no longer reproducible in 27.2 and does seem to be fixed. Please retry and open a new ticket should this still persist for you.
To:
>there is no width attribute in the <image> tag
This has been fixed.
To:
> We are using "data-name" attribute to manage elements color, text etc in webApps. It is very critical for us.
Please add more details about your workflow. Ideally create a new ticket.
To:
>.st0{fill:url(#Element1_00000070839701103496739130000017927991525955991726_);}
Please try the Asset Export panel or File > Export which should not have this issue.