Skip to content

brian bosch

My feedback

5 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    brian bosch commented  · 

    I submitted my files to the requested email address. the full text from the SVG file is in my initial post, however I just noticed that underlines (_) were removed from the SVG code and the indents are removed. here are the SVG's with the extension changed to .txt

    An error occurred while saving the comment
    brian bosch commented  · 

    Continued:

    From what I can see this has been a bug in the Illustrator SVG export for a long time, but legacy Javascript SVG export took care of irregular characters. The new export process treats non alpha-numeric characters differently, and doesn't replace periods (.). I believe this was an issue that arose back in 2022 when the File/Export option started using the updated SVG spec, and is now an issue as of Version 28.4.1 with the same switch in the Save As\SVG process.
    From what I can see the only solution offered has been to tell the users to switch to using 'Style Attributes" in their SVG CSS settings, but this isn't helpful for anyone who uses custom CSS style labels for post processing, exports using developer options, and requires Style driven CSS for HTML or interactive SVG’s. It simply ignores the issue.

    This needs to be addressed. If the export process itself cannot be changed then the menu needs to be changed to not accept periods (.) in Graphic Style names, to remove periods in legacy documents when exported to SVG, or notify the user that these characters exist and should be replaced. This is now an issue in the Save As and Export options for producing SVG’s.

    brian bosch shared this idea  · 
  2. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    brian bosch supported this idea  · 
  3. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    brian bosch supported this idea  · 
  4. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This change is intentional. The team aims to improve the way SVG is generated (speed, size, redundancy, etc.) and merge current both code branches into one.

    Since some workflows heavily rely on the way the code structure is organized, the team tries to gather feedback on it.

    Please describe what engine changes affect you and why.

    brian bosch supported this idea  · 
  5. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    brian bosch supported this idea  · 

Feedback and Knowledge Base