monokano
My feedback
-
46 votes
Hello All,
Thank you for reporting the issue to us.
We have fixed the issue in the latest version of InDesign, Id 15.0Please upgrade your InDesign application to the latest version to try out the fix.
If you face any problems with the new update, do let us know in the comments.
You may also follow the below given link for the list of all fixed issues in Id 15.0
https://helpx.adobe.com/indesign/kb/fixed-issues.html-InDesign Team
monokano
supported this idea
·
-
8 votes
This thread has been marked Under Review.
One of the major usecases is still yet to be addressed.monokano
supported this idea
·
-
213 votesmonokano
supported this idea
·
An error occurred while saving the comment -
9 votesmonokano
supported this idea
·
-
10 votes
This issue has been fixed in one of the updates to InDesign.
—
Adobe InDesign teammonokano
supported this idea
·
-
38 votes
This has been done to preclude any new entries for CFBundleTypeOSTypes. The previous release, CC2018 had CFBundleTypeOSType as IDdD but for the new release, we have not created the new OSType entry as IDdE rather kept the previos entry intact.
Apple had deprecated any entries of the form of CFBundleType from 10.5 and now recommends using a UTType(Uniform Type Identifier) entry instead of creating CFBundleType entries. We might choose creating UTTypes in the future. However, for now we have stopped creating separate CFBundleTypes for the new releases.
It would helpful to know from you as to how you use these entries in your workflows so that we can suggest you an alternative.You may reach out to abkaushi@adobe.com.
An error occurred while saving the comment monokano
commented
Hi Abhinav
I understand that migration to UTI is inevitable.First of all, we hope to be able to get the created version of the indd file accurately and quickly. This is a long-standing desire.
About accuracy;
Bridge.app displays the application information (XMP:CreatorTool) in indd, but this version may be inaccurate. We can not trust this information.About quickness;
To know the real creation version in indd, we have to open that file, hold down the modifier key and select the About menu and watch the history. While dealing with large numbers of indd files, it is impractical to do this operation.Filetype (CFBundleType OSType) was an attribute that can get version information accurately and quickly without opening a file. If this is gone, only the binary at the top of the file will remain. But this is more difficult for the user than Filetype.
We lose the means to get the creation version of the indd file accurately and quickly. We hope this problem will be solved.
An error occurred while saving the comment monokano
commented
Hi Abhinav
1.
Filetype is CFBundleDocumentTypes in Info.plist. In particular, the 4-character CFBundleTypeOSTypes is the same IDdD for both CC 2018 and 2019 InDesign documents.This attribute was unique to each version. Using this wonderful attribute I make my own desktop application and use it. This app displays file icons by version, and also displays Kind of Finder information by version. I am disappointed because CC 2019 can not do this. There may be people besides me who use this wonderful attribute.
2.
All available versions are installed.The indd file made with the old version will be revised in later years. These must be opened in the same version. The indd file made from various versions come from the outside. These must be opened with the same version at this time. In order to deal with these, all available versions are installed.
monokano
shared this idea
·
-
15 votes
Hello All,
Thank you for your support. The issue is now fixed in the latest update of InDesign.
Please upgrade to the new InDesign 14.0 from your Creative Cloud Application.If you are unable to see the update yet, click on the menu (three dots) on the top right corner of Creative cloud app and click on “Check for App Updates”.
Let us know your feedback in the comment section.
Thanks,
Abhinav Kaushik
InDesign Teammonokano
supported this idea
·
-
79 votes8 comments · Adobe InDesign: Feature Requests » Text and Type · Flag idea as inappropriate… · Admin →
Hi,
Am moving this issue as a feature request. The idea here is to achieve an effect like: https://app.box.com/s/2eflfbxwychhln9f34tpf0yyw898w5dhCurrently this can be done by turning off the bottom border of the last frame and top border of the first frame.
-Aman
An error occurred while saving the comment monokano
commented
Please see the sample.
An error occurred while saving the comment monokano
commented
Hi Aman
The purpose of merging the borders is to visually represent that it is A UNIT.
This representation must be maintained even when split in thread text frames.
When divided, the meaning will change.
Please do not divide as document structure.monokano
shared this idea
·
Many Japanese users have complained about this, too.
All users customize their preferences. After delete preference files is done, our customized preferences also disappear (it returns to the default setting). Whenever we do delete preference files, we have to recover them one by one, again, and again, and again.... This recovery work is a huge problem. This extra workflow wastes a lot of our times always. I request new feature that restores the user’s customize preferences at the same time as delete preference files.
Japanese translation:
多くの日本のユーザーもこれについて不満を言っています。
すべてのユーザーは環境設定をカスタマイズしています。しかし、環境設定の初期化で関連ファイルの削除が行われると、その度にデフォルトに戻り、カスタマイズした設定が消失してしまいます。この消失はきわめて大きな問題です。その度に設定をしなおすことになり、ユーザーは常に過重な負担を強いられています。これを改善する方法として、環境設定初期化時にユーザーのカスタマイズ設定を自動復元する機能をリクエストします。