The idea of cloud docs is wonderful, but the reality is intensely frustrating.

File created in the studio; a simple text logo. Retun home need to make a change. Impossible to open.

"Make file available offline" Done. Still impossible to open.

Identical version of Illustrator on both Macs. Multiple occurrences. It has happened in reverse too

Workaround > Store files on a disk. Transfer manually. (Not what Adobe want to hear!)

I should add that this a a regular problem on PS too, so a broader Creative Cloud, issue. Oh and the internet connection is Gigabit, so not a speed issue.

We need to add files and dimensions when exporting for screens every single time when working with a new document. Presets need to be stored globally across documents. If you could also store not just one file export setup but multiple user named presets, that would be awesome! Like different export lists, not just one. Illustrator does not remember my file list, sometimes yes, sometimes no. Its a mess. I often need to re-enter my list in other documents and often also in the same document (when appending the list). That is a total of 40 export files and dimensions variations I have to enter every time. The current setup is a work-flow killer. There are multiple forum entries and also one here for "Asset Export". But we need globally stored multiple preferences for both asset export AND "Export for Screens". Thanks for your hard work.

macOS 11.5.1 / Adobe Illustrator 25.3.1

[on macOS] when saving files only the filename is selecetd, not the extension. It used to be fine with Adobe apps until some versions back suddenly the whole file name including extension is selected in the Save as dialog.

Adding some text used to be easy. With a tap on the right arrow key the cursor moved between de file name and the extension. When I do this now the cursor is placed after the extension so I have to use the mouse or left arrow key to move the cursor 3-4 positions back. This may be OK on Windows but it is definately not Mac behaviour.

Please fix it.

Enclosed is a sample how a Save as dialog should behave in macOS.

Recently, my business has been doing a lot of acrylic construction tags for Electricians, and HVAC companies, and Illustrator is generally our "go to" software suite when developing files for our clients, but with the recent work that has been coming in to our company, we have begun to explore the variable data features in Illustrator, and have found this feature to be less than ideal, and is currently not a viable alternative to the way we have been doing things thusfar.

Currently, it seems the variables that one would set up in a given design file are referenced, or linked to a single row containing data in the file, and does not allow the user to set up multiple rows of variable data, within the same design file.

Some of the equipment control software in our shop seems to let us setup the process files in a manner that does let users pull indepenent columns of data, and then allows the user to sort that data by row in setting up the file.

That being said, the variable data software that is found in that particular equipment, is not found in the equipment/control software that is used to process these tags, so Illustrator would hopefully provide an answer to that dilemma (if it had the ability to set up the variable data to independently populate text fields, within the design file, in a more efficient manner).

I wanted to export a TGA from .ai file but I want to keep only elements which are present in the artboard not which are out of the artboard.

There is a 'User artboard' option to avoid unwanted elements outside the artboard but it is inactive for exporting TGA. Due to which after exports all the elements which are outside of artboard will also be exported.

By making 'User artboard' option active for TGA will solve this issue

While exporting the TGA from .ai file, the user should be able to choose the 'User artboard' option. Curretly it is inactive for TGA.

Relative links are absolutely essential for collaborating on common projects in an agency.

It's so annoying to work together on a project. When my collaborator starts an Illustrator file and I want to work on it, all links are broken, vice versa the same and the cycle never ends. Sometimes I don't even know what folder some linked files are stored in, so it's impossible to continue his work without his help!

Everyone who works together on bigger projects has this problem, especially in times of home office.

I figured the Creative Cloud wasn't just meant to be a backup storage. But as it is, it's not useful for much else, unfortunately.

Please, at least add an option for that.

現在、IllustratorではXMPメタデータ上のHistoryの記述が最大で２個となっていて、初回保存時に１つ目、別名で保存時に２つ目が記述され、以降、別名で保存によるファイル派生が生じた時に２つ目のHistoryが更新される仕様になっています。
Photoshopでは、このHistoryの項目に保存履歴だけではなくconvertやderived等の主要な編集イベントの情報も記述されます。InDesignにおいても保存イベントは詳細に記述され履歴の確認が可能になっています。
Illustratorにおいても、もう少し細かく履歴情報の記述を行っていただきたい。

以下に各サンプルを挙げておきます。
※Photoshop
＜xmpMM:History＞
＜rdf:Seq＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞saved＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:fa197c48-1372-49d9-8ae1-f5cc273d4aae＜/stEvt:instanceID＞
＜stEvt:when＞2019-01-25T20:48:06+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe Photoshop CC 2017 (Macintosh)＜/stEvt:softwareAgent＞
＜stEvt:changed＞/＜/stEvt:changed＞
＜/rdf:li＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞converted＜/stEvt:action＞
＜stEvt:parameters＞from image/jpeg to application/vnd.adobe.photoshop＜/stEvt:parameters＞
＜/rdf:li＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞derived＜/stEvt:action＞
＜stEvt:parameters＞converted from image/jpeg to application/vnd.adobe.photoshop＜/stEvt:parameters＞
＜/rdf:li＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞saved＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:779a3d47-4ae6-4b0e-be0b-b1a7f2ee5007＜/stEvt:instanceID＞
＜stEvt:when＞2019-01-25T20:48:06+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe Photoshop CC 2017 (Macintosh)＜/stEvt:softwareAgent＞
＜stEvt:changed＞/＜/stEvt:changed＞
＜/rdf:li＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞saved＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:f343692b-df77-40bb-8ee4-6fefc6341435＜/stEvt:instanceID＞
＜stEvt:when＞2019-06-05T21:28:08+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe Photoshop CC 2017 (Macintosh)＜/stEvt:softwareAgent＞
＜stEvt:changed＞/＜/stEvt:changed＞
＜/rdf:li＞
＜/rdf:Seq＞
＜/xmpMM:History＞

保存以外の様々なイベントが記述され確認が可能です。

※InDesign
＜xmpMM:History＞
＜rdf:Seq＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞created＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:FC7BA4FD42206811822A93784E262F37＜/stEvt:instanceID＞
＜stEvt:when＞2012-05-11T15:56:45+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe InDesign 7.0＜/stEvt:softwareAgent＞
＜/rdf:li＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞saved＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:CEC84C1347206811822A93784E262F37＜/stEvt:instanceID＞
＜stEvt:when＞2012-05-11T16:26+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe InDesign 7.0＜/stEvt:softwareAgent＞
＜stEvt:changed＞/;/metadata＜/stEvt:changed＞
＜/rdf:li＞
・
・
・
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞saved＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:3aa516e9-6e10-4d30-8213-1d01b5e0c6e8＜/stEvt:instanceID＞
＜stEvt:when＞2021-05-18T19:03:52+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe InDesign 16.1 (Macintosh)＜/stEvt:softwareAgent＞
＜stEvt:changed＞/metadata＜/stEvt:changed＞
＜/rdf:li＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞saved＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:8dc6f9ce-5068-4b44-8ca1-832341fcf4f1＜/stEvt:instanceID＞
＜stEvt:when＞2021-05-19T09:16:49+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe InDesign 16.1 (Macintosh)＜/stEvt:softwareAgent＞
＜stEvt:changed＞/＜/stEvt:changed＞
＜/rdf:li＞
＜rdf:li rdf:parseType="Resource"＞
＜stEvt:action＞saved＜/stEvt:action＞
＜stEvt:instanceID＞xmp.iid:fee74c32-8ae2-46e4-9ef9-fc8a432d7f5a＜/stEvt:instanceID＞
＜stEvt:when＞2021-05-24T17:08:14+09:00＜/stEvt:when＞
＜stEvt:softwareAgent＞Adobe InDesign 16.1 (Macintosh)＜/stEvt:softwareAgent＞
＜stEvt:changed＞/＜/stEvt:changed＞
＜/rdf:li＞
＜/rdf:Seq＞
＜/xmpMM:History＞

createdイベント以降詳細に保存履歴が記述されます。

この例のように全ての保存を記述する必要性は低いと思いますが最低限、別名で保存や複製を保存時には新たな履歴を追記するようにしていただきたいと考えます。

これにより、ファイルの履歴が明確になりデータ管理の一助となります。