E-mail List Archives
Re: More Adobe Acrobat Accessibility Errors
From: Ilana Gordon
Date: Apr 4, 2019 2:16PM
- Next message: Philip Kiff: "Re: More Adobe Acrobat Accessibility Errors"
- Previous message: Karlen Communications: "Re: More Adobe Acrobat Accessibility Errors"
- Next message in Thread: Philip Kiff: "Re: More Adobe Acrobat Accessibility Errors"
- Previous message in Thread: Karlen Communications: "Re: More Adobe Acrobat Accessibility Errors"
- View all messages in this Thread
I've been monitoring this conversation closely and have one additional
question about the conversion from Word to PDF? I have both PC and MAC
versions of Word. I use Acrobat DC. It seems that both Microsoft and Adobe
have created a seemless and effective export with tags. But.... the
documents are sent to either Microsoft's cloud or Adobe's cloud if you use
the export features and not save as.
The big question by using that process does Adobe or Microsoft have use of
those documents and/or own them on the cloud and thus creating a security
and intellectual property ownership issue?
Looking forward to some answers on that!
Ilana Gordon
On Thu, Apr 4, 2019 at 4:03 PM Karlen Communications <
<EMAIL REMOVED> > wrote:
> I haven't had problems with EN-CA. I notice that when I use the
> Word/Microsoft conversion tool the primary language for the document I'm
> working on is English which is correct. You always want to have a generic
> language identified as the primary language (or on any Tags in a
> multilingual document) so that if a localized version of the language is
> not supported, the person can use their default generic language
> synthesizer/voice.
>
> It also lets someone listen to the document with pronunciations they are
> used to hearing. For example, I use Eloquence with the British voice. If I
> have to listen to content using different pronunciations (for example
> American English), it takes me quite a while to understand what I'm reading
> and I imagine the same can be said for those using American English as
> their default synthesizer language who may have to listen to British
> pronunciations.
>
> Maybe this is a change Word to snag a generic language and the Adobe
> conversion tool hasn't caught up to this yet. I would still think that they
> should be able to snag the language from somewhere in the document.
>
> Cheers, Karen
>
>
>
- Next message: Philip Kiff: "Re: More Adobe Acrobat Accessibility Errors"
- Previous message: Karlen Communications: "Re: More Adobe Acrobat Accessibility Errors"
- Next message in Thread: Philip Kiff: "Re: More Adobe Acrobat Accessibility Errors"
- Previous message in Thread: Karlen Communications: "Re: More Adobe Acrobat Accessibility Errors"
- View all messages in this Thread