Ten
My feedback
-
17 votes
Hello All,
The fix for this issue is now available in the beta builds of InDesign. You can download the latest beta build from Download section of InDesign Prerelease portal.
1. Go to adobeprerelease.com
2. Log in with your Adobe Id.
3. Once logged in, search for “InDesign CC Prerelease” program in the list.
4. Click on the program to join the same.
5. You can now download the build (14.0.3.422) from “Builds and Plugins” section on the page.
6. The steps for installing the build can be found in the release notesTen
shared this idea
·
-
45 votes
Hello All,
The fix for this issue is now available in the beta builds of InDesign. You can download the latest beta build from Download section of InDesign Prerelease portal.
1. Go to adobeprerelease.com
2. Log in with your Adobe Id.
3. Once logged in, search for “InDesign CC Prerelease” program in the list.
4. Click on the program to join the same.
5. You can now download the build (14.0.3.422) from “Builds and Plugins” section on the page.
6. The steps for installing the build can be found in the release notesTen
supported this idea
·
-
135 votesTen
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.Ten
supported this idea
·
-
9 votes0 comments · Adobe InDesign: Feature Requests » Print/Packaging · Flag idea as inappropriate… · Admin →Ten
supported this idea
·
日本語にて概要を説明しておきます。
InDesignはQRコード作成機能搭載の当初から日本語特有の漢字モードを正常に処理出来ず、日本語の混ざった文字列を正常にQRコード化出来ないというバグがあり、現在まで修正されないままです。
これは漢字モード自体の実装と漢字モードへの移行判定のバグという２本立ての不具合を抱えていることに起因するものです。
私が推奨したいシナリオは「漢字モードを廃止し8bitバイトモード固定での運用及びマルチバイトを含め全てをUTF-8文字列として扱うこと」です。これによりウムラウト等のノンアスキーキャラクタの問題も解消可能となります。