跳至主要内容

Adobe Document Cloud not in Chinese UI

Recent days I’ve been reading Erlang related PDF, so I have a chance to write some private notes for later review. As it is a mobile century now, we never work on single device anymore. I would like to sync all my notes and my reading progress across different devices.

With some time-consuming googling work finished, I find there’s two ready to be used solution that is able to fulfill my personal needs:

  • Adobe Acrobat Reader DC + Acrobat Reader mobile + Document Cloud
  • Foxit PDF reader + Foxit connected PDF service

The result surprised me, because I’ve been using Acrobat Reader DC for about a year now, but never notice it is able to sync anything to Adobe managed cloud storage named Document Cloud. In fact, I’ve been wondering for years why Acrobat Reader renamed as Acrobat Reader DC in recent update and what does that ‘DC’ mean.

Now comes to real life practice with the Document Cloud feature. It is wonderful, Acrobat Reader for android is able to manage PDF files in Document Cloud just inside the app. Anyway when comes to the Acrobat Reader DC for windows, the long history Acrobat Reader I’ve been known for years, I can not find anything Document Cloud related except that there’s a hyperlink opens an external browser to update my AdobeID details.

How can this happen when there’s plenty of on-line help and document describe the Document Cloud feature not exist in reality? Today I just find the answer accidentally by switching my UI language from simplified Chinese to English. All Document Cloud related menus and buttons just appear like a magic.

Okay, I am not complaining about anything, just write this down for later reference.

You may also ask, “why not just foxit reader? It has integrated cloud service at first place too, and it was much lightweight than adobe one”. While, if you are a Chinese user with devices in China market, you may now understand my feeling as a free account user of foxit. Their Chinese version on mobile device, android specifically, carries too much unnecessary feature and ADs that I can’t afford to use when all what I need is just a reader with notes and progress synchronization.

 

标签：

评论

发表评论

此博客中的热门博文

Use MobaDiff with git difftool

Recently there's an activity in IT that forces the deletion of all unauthorized softwares from all work machines. Unfortunately, kdiff3 is one in the list. As it is generally okay to use vimdiff as an alternative for kdiff3, A gui tool is better suited for desktop workflows. Known that MobaXterm is shipping a gui diff tool named MobaDiff. But it only appears in the windows right click context menu. Find the real application name takes me some time to search in the windows registry. "MobaRTE.exe", which is the one invoked by HKCR\*\shell\MobaDiff. And it was invoked with "-contextdiff" switch to show MobaDiff UI, while when the switch is "-contextedit" it shows MobaTextEditor. Too bad that the "-contextdiff" switch do not support pre-image post-image as other diff tool did, which effectively made it unable to be used as a command line diff utility. Also MobaTech did not mention anything in their document of this Mob...
发表评论
阅读全文

Emacs 26.2 windows Hunspell setup

 Hunspell failed with default setup With my shining new emacs26.2 setup, I am happy until trying to `M-$’ on a word. I got following error message, it used to be work by just set ispell program to hunspell. Starting new Ispell process hunspell with default dictionary... split-string: Wrong type argument: stringp, nil After some check in my customization setting. nothing found. install a copy of hunspell dictionary At first I think it was caused by no hunspell dictionary. I downloaded en US and en CA hunspell dictionary from wordlist.sf.net project. After put the .aff and .dic files into C:directory I’ve also made a symbolic link from en US ones by running the `mklink’ tool: mklink default.aff en_US.aff mklink default.dic en_US.dic Err… hunspell does not work, still. Time to read code Dig into ispell.el I suprisingly find there’re lots of hunspell specific logic. Originally I was thinking hunspell support involves no elisp work. Acturally ispell did many work to de...
发表评论
阅读全文

XEmacs 21.5 beta 35 "kohlrabi" has been released.

If you are an old XEmacs user, you may feel happy to see this from https://www.xemacs.org/.    After ten years, XEmacs released a new version 21.5. So there's still many people cares about XEmacs. The XEmacs' source repo have been moved from altassian Bitbucket to https://heptapod.net/. As Bitbucket have been dropped Mercurial support many years ago.
发表评论
阅读全文