Hi Cyrille.
In fact it is very simple.
For my personnal use, I use "instantTranslate" to translate, on demand, the emails I receive on Thunderbird.
So I created the "getTranslation" method using part of the "translate" method and modified the "translate" method like this:
En fait c'est tout simple.
J'utilise "instantTranslate" pour traduire, à la demande, les mails que je reçois sur Thunderbird.
Donc j'ai créé la méthode "getTranslation" en utilisant une partie de la méthode "translate" et modifié la méthode "translate" comme ceci:
def getTranslation(self, text):
        self.getUpdatedGlobalVars()
        global lang_from
        # useful for yandex, that doesn't support auto option
#        if lang_from == "auto":
#            lang_from = detect_language(text)
        translation = None
        if (text, lang_to, lang_from) in [(x[0],x[1],x[2]) for x in self.cachedResults]:
            translation,lang = [f for f in self.cachedResults if f[0] == text and f[1] == lang_to and f[2] == lang_from][0][3:5]
            index = [(te,lt,lf,tr) for te, lt, lf, tr, lg in self.cachedResults].index((text, lang_to, lang_from, translation))
            self.addResultToCache(text, translation, lang, removeIndex=index)
        else:
            myTranslator = None
            if not autoSwap:
                myTranslator = Translator(lang_from, lang_to, text)
            else:
                myTranslator = Translator(lang_from, lang_to, text, lang_swap)
            myTranslator.start()
            i=0
            while myTranslator.is_alive():
                sleep(0.1)
                i+=1
                if i == 10:
                    beep(500, 100)
                    i = 0
            myTranslator.join()
            translation = myTranslator.translation
            lang = myTranslator.lang_to
            if translation != '':
                self.addResultToCache(text, translation, lang)
        msgTranslation = {'text': translation, 'lang': lang}
        self.copyResult(translation)
        return (translation, lang)

    def translate(self, text):
        (translation, lang) = self.getTranslation(text)
        msgTranslation = {'text': translation, 'lang': lang}
        queueHandler.queueFunction(queueHandler.eventQueue, messageWithLangDetection, msgTranslation)
        self.copyResult(translation)



Then just call the "getTranslation" method from another add-on to have the translation of any text.
Il suffit alors d'appeler la méthode "getTranslation"  à partir d'un autre add-on pour avoir la traduction de n'importe quel texte.

Best regards.
Paul.

Le 06/05/2020 12:27, Cyrille via groups.io a écrit :

Hi Paul

This is not clear to me. Could you elaborate with step-by-step instructions, expected result and real-life example?

In English here or in French in a private message or on French mailing lists.

Cheers,

Cyrille

Le 06/05/2020 à 11:46, bering.p a écrit :

Hi.
I take this opportunity because I also have a request for this add-on.
I would like it to provide the ability to process a translation request from another add-on and return the translation to that add-on.
Thank you.
Best regards.
Paul.

Le 06/05/2020 11:25, Norberto Sousa a écrit :

Hi,

By the way that you're working the addon...

I didn't know if I got it quite well, but when Source language is set to Automatic, Target language is set to Portuguese, and Swap language is set to English, when you translate a text from portuguese it should change automatically, right? If so, it is not working.

- In comboboxes to select languages you can only press the first letter of the language to jump to it. Can you work it around to be possible to press the two-three first letters?

- If you can make the introduction help text simpler. It is a bit confusing.

Kind regards,

NSousa

On Tue, May 5, 2020 at 11:31 PM Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:

Hello Beqa


Oops, sorry, seems that I have forgotten a step.

Since there has been new commits in nvdaaddons/stable that were not yet
pulled in beqabeqa473/stable, you will not be able to perform fast
forward merge of beqabeqa473/stable in nvdaaddons/stable.

So you should:

1. Delete the merge commit you have just done, i.e. reset
beqabeqa473/stable to its previous position.

2. Merge nvdaaddons/stable into beqabeqa473/stable

3. Merge beqabeqa473/master into beqabeqa473/stable. And tag a new
release if you want.

4. Ask to have beqabeqa473/stable merged into nvdaaddons/stable and new
release published. You may also ask to have beqabeqa473/master merged
into nvdaaddons/master.

5. Update the documentation on the website (.mdwn file) or ask someone
to do it for you. I can do it if you need.

After some time when translators have updated translations:

6. Merge nvdaaddons/stable into beqabeqa473/stable

7. Merge beqabeqa473/stable into beqabeqa473/master.


This time I think I have not forgotten anything.

Cheers,


Cyrille


Le 05/05/2020 à 18:24, Beqa Gozalishvili a écrit :
> hi.
>
> i've merged master into stable
>
> thanks.
>
> On 5/5/20, Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:
>> Hello Beqa
>>
>>
>> Since you seem to have time these days, could you please do the
>> following regarding InstantTranslate:
>>
>> * Update the strings to translate for translators. Indeed, translation
>> of this add-on has not been updated for many years, even if this add-on
>> is already in the translation system. For this, you need to merge master
>> into stable and ask to push your new stable branch to nvdaaddons'
>> InstantTranslate repo.
>>
>> * Make a new release containing unpublished last commits (restore
>> language detection, new languages addition)) as well as new translation
>> when they will be available. For this, you will need to update your
>> stable branch from nvdaaddons' stable branch (containing future new
>> translations) and merge stable into master to get new translations in
>> the master branch.
>>
>>
>> Could you also tag the future releases in GIT so that we can follow more
>> easily releases in GIT?
>>
>>
>> If something is not clear or if you remain stuck somewhere, do not
>> hesitate to ask.
>>
>> Thanks.
>>
>> Cheers,
>>
>>
>> Cyrille
>>
>>
>>
>>
>>
>>
>

--

Norberto Inácio de Sousa
Consultor de acessibilidade Web e digital;
Formador de acessibilidade, informática e línguas;
https://www.linkedin.com/in/norberto-in%C3%A1cio-de-sousa-a129ab4b/
Tlm. 962836137

Hi Paul

This is not clear to me. Could you elaborate with step-by-step instructions, expected result and real-life example?

In English here or in French in a private message or on French mailing lists.

Cheers,

Cyrille

Le 06/05/2020 à 11:46, bering.p a écrit :

Hi.
I take this opportunity because I also have a request for this add-on.
I would like it to provide the ability to process a translation request from another add-on and return the translation to that add-on.
Thank you.
Best regards.
Paul.

Le 06/05/2020 11:25, Norberto Sousa a écrit :

Hi,

By the way that you're working the addon...

I didn't know if I got it quite well, but when Source language is set to Automatic, Target language is set to Portuguese, and Swap language is set to English, when you translate a text from portuguese it should change automatically, right? If so, it is not working.

- In comboboxes to select languages you can only press the first letter of the language to jump to it. Can you work it around to be possible to press the two-three first letters?

- If you can make the introduction help text simpler. It is a bit confusing.

Kind regards,

NSousa

On Tue, May 5, 2020 at 11:31 PM Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:

Hello Beqa


Oops, sorry, seems that I have forgotten a step.

Since there has been new commits in nvdaaddons/stable that were not yet
pulled in beqabeqa473/stable, you will not be able to perform fast
forward merge of beqabeqa473/stable in nvdaaddons/stable.

So you should:

1. Delete the merge commit you have just done, i.e. reset
beqabeqa473/stable to its previous position.

2. Merge nvdaaddons/stable into beqabeqa473/stable

3. Merge beqabeqa473/master into beqabeqa473/stable. And tag a new
release if you want.

4. Ask to have beqabeqa473/stable merged into nvdaaddons/stable and new
release published. You may also ask to have beqabeqa473/master merged
into nvdaaddons/master.

5. Update the documentation on the website (.mdwn file) or ask someone
to do it for you. I can do it if you need.

After some time when translators have updated translations:

6. Merge nvdaaddons/stable into beqabeqa473/stable

7. Merge beqabeqa473/stable into beqabeqa473/master.


This time I think I have not forgotten anything.

Cheers,


Cyrille


Le 05/05/2020 à 18:24, Beqa Gozalishvili a écrit :
> hi.
>
> i've merged master into stable
>
> thanks.
>
> On 5/5/20, Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:
>> Hello Beqa
>>
>>
>> Since you seem to have time these days, could you please do the
>> following regarding InstantTranslate:
>>
>> * Update the strings to translate for translators. Indeed, translation
>> of this add-on has not been updated for many years, even if this add-on
>> is already in the translation system. For this, you need to merge master
>> into stable and ask to push your new stable branch to nvdaaddons'
>> InstantTranslate repo.
>>
>> * Make a new release containing unpublished last commits (restore
>> language detection, new languages addition)) as well as new translation
>> when they will be available. For this, you will need to update your
>> stable branch from nvdaaddons' stable branch (containing future new
>> translations) and merge stable into master to get new translations in
>> the master branch.
>>
>>
>> Could you also tag the future releases in GIT so that we can follow more
>> easily releases in GIT?
>>
>>
>> If something is not clear or if you remain stuck somewhere, do not
>> hesitate to ask.
>>
>> Thanks.
>>
>> Cheers,
>>
>>
>> Cyrille
>>
>>
>>
>>
>>
>>
>

--

Norberto Inácio de Sousa
Consultor de acessibilidade Web e digital;
Formador de acessibilidade, informática e línguas;
https://www.linkedin.com/in/norberto-in%C3%A1cio-de-sousa-a129ab4b/
Tlm. 962836137

Hi.
I take this opportunity because I also have a request for this add-on.
I would like it to provide the ability to process a translation request from another add-on and return the translation to that add-on.
Thank you.
Best regards.
Paul.

Le 06/05/2020 11:25, Norberto Sousa a écrit :

Hi,

By the way that you're working the addon...

I didn't know if I got it quite well, but when Source language is set to Automatic, Target language is set to Portuguese, and Swap language is set to English, when you translate a text from portuguese it should change automatically, right? If so, it is not working.

- In comboboxes to select languages you can only press the first letter of the language to jump to it. Can you work it around to be possible to press the two-three first letters?

- If you can make the introduction help text simpler. It is a bit confusing.

Kind regards,

NSousa

On Tue, May 5, 2020 at 11:31 PM Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:

Hello Beqa


Oops, sorry, seems that I have forgotten a step.

Since there has been new commits in nvdaaddons/stable that were not yet
pulled in beqabeqa473/stable, you will not be able to perform fast
forward merge of beqabeqa473/stable in nvdaaddons/stable.

So you should:

1. Delete the merge commit you have just done, i.e. reset
beqabeqa473/stable to its previous position.

2. Merge nvdaaddons/stable into beqabeqa473/stable

3. Merge beqabeqa473/master into beqabeqa473/stable. And tag a new
release if you want.

4. Ask to have beqabeqa473/stable merged into nvdaaddons/stable and new
release published. You may also ask to have beqabeqa473/master merged
into nvdaaddons/master.

5. Update the documentation on the website (.mdwn file) or ask someone
to do it for you. I can do it if you need.

After some time when translators have updated translations:

6. Merge nvdaaddons/stable into beqabeqa473/stable

7. Merge beqabeqa473/stable into beqabeqa473/master.


This time I think I have not forgotten anything.

Cheers,


Cyrille


Le 05/05/2020 à 18:24, Beqa Gozalishvili a écrit :
> hi.
>
> i've merged master into stable
>
> thanks.
>
> On 5/5/20, Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:
>> Hello Beqa
>>
>>
>> Since you seem to have time these days, could you please do the
>> following regarding InstantTranslate:
>>
>> * Update the strings to translate for translators. Indeed, translation
>> of this add-on has not been updated for many years, even if this add-on
>> is already in the translation system. For this, you need to merge master
>> into stable and ask to push your new stable branch to nvdaaddons'
>> InstantTranslate repo.
>>
>> * Make a new release containing unpublished last commits (restore
>> language detection, new languages addition)) as well as new translation
>> when they will be available. For this, you will need to update your
>> stable branch from nvdaaddons' stable branch (containing future new
>> translations) and merge stable into master to get new translations in
>> the master branch.
>>
>>
>> Could you also tag the future releases in GIT so that we can follow more
>> easily releases in GIT?
>>
>>
>> If something is not clear or if you remain stuck somewhere, do not
>> hesitate to ask.
>>
>> Thanks.
>>
>> Cheers,
>>
>>
>> Cyrille
>>
>>
>>
>>
>>
>>
>

--

Norberto Inácio de Sousa
Consultor de acessibilidade Web e digital;
Formador de acessibilidade, informática e línguas;
https://www.linkedin.com/in/norberto-in%C3%A1cio-de-sousa-a129ab4b/
Tlm. 962836137

Hi,

By the way that you're working the addon...

I didn't know if I got it quite well, but when Source language is set to Automatic, Target language is set to Portuguese, and Swap language is set to English, when you translate a text from portuguese it should change automatically, right? If so, it is not working.

- In comboboxes to select languages you can only press the first letter of the language to jump to it. Can you work it around to be possible to press the two-three first letters?

- If you can make the introduction help text simpler. It is a bit confusing.

Kind regards,

NSousa

On Tue, May 5, 2020 at 11:31 PM Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:

Hello Beqa


Oops, sorry, seems that I have forgotten a step.

Since there has been new commits in nvdaaddons/stable that were not yet
pulled in beqabeqa473/stable, you will not be able to perform fast
forward merge of beqabeqa473/stable in nvdaaddons/stable.

So you should:

1. Delete the merge commit you have just done, i.e. reset
beqabeqa473/stable to its previous position.

2. Merge nvdaaddons/stable into beqabeqa473/stable

3. Merge beqabeqa473/master into beqabeqa473/stable. And tag a new
release if you want.

4. Ask to have beqabeqa473/stable merged into nvdaaddons/stable and new
release published. You may also ask to have beqabeqa473/master merged
into nvdaaddons/master.

5. Update the documentation on the website (.mdwn file) or ask someone
to do it for you. I can do it if you need.

After some time when translators have updated translations:

6. Merge nvdaaddons/stable into beqabeqa473/stable

7. Merge beqabeqa473/stable into beqabeqa473/master.


This time I think I have not forgotten anything.

Cheers,


Cyrille


Le 05/05/2020 à 18:24, Beqa Gozalishvili a écrit :
> hi.
>
> i've merged master into stable
>
> thanks.
>
> On 5/5/20, Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:
>> Hello Beqa
>>
>>
>> Since you seem to have time these days, could you please do the
>> following regarding InstantTranslate:
>>
>> * Update the strings to translate for translators. Indeed, translation
>> of this add-on has not been updated for many years, even if this add-on
>> is already in the translation system. For this, you need to merge master
>> into stable and ask to push your new stable branch to nvdaaddons'
>> InstantTranslate repo.
>>
>> * Make a new release containing unpublished last commits (restore
>> language detection, new languages addition)) as well as new translation
>> when they will be available. For this, you will need to update your
>> stable branch from nvdaaddons' stable branch (containing future new
>> translations) and merge stable into master to get new translations in
>> the master branch.
>>
>>
>> Could you also tag the future releases in GIT so that we can follow more
>> easily releases in GIT?
>>
>>
>> If something is not clear or if you remain stuck somewhere, do not
>> hesitate to ask.
>>
>> Thanks.
>>
>> Cheers,
>>
>>
>> Cyrille
>>
>>
>>
>>
>>
>>
>

--

Norberto Inácio de Sousa
Consultor de acessibilidade Web e digital;
Formador de acessibilidade, informática e línguas;
https://www.linkedin.com/in/norberto-in%C3%A1cio-de-sousa-a129ab4b/
Tlm. 962836137

Hello NVDA add-ons community,

First, to our new friends: I am sorry for letting you have an unpleasant experience today. The add-ons community could have done things better in regards to latest thread (just closed).

The last few days (and weeks) have been quite an emotional journey for me and the community. In the midst of celebrating release of NVDA 2020.1 RC and new add-ons, we felt exhausted and frustrated. Personally, after reading the latest thread (messages coming in as I slept), I felt disappointed, at one point feeling angry as a post from a member appeared to defy requests from a moderator (I understand the frustration). At times I felt I wasn’t doing my volunteer job as an add-on reviewer, at times navigating my internal struggles due to school, at other times trying to plan ahead for post-COVID-19 world, and feeling trapped at home, unable to go out and do anything except show my online presence. These stresses, along with exhaustion and frustration from community members, became a fuel for flames and thread hijacking, one of the reasons behind this community-wide notice.

A few things to say about recent happenings, this time not as a member of this list or an add-on reviewer, but as your list administrator:

First, from the bottom of my heart, I ask everyone to NEVER AGAIN hijack a thread. If you read about an add-on release and get a strong feeling to reply and tell us to review your own add-ons, please don’t do that anymore. This is more so after one such reply became a fuel for the flame we saw today.

So what should you do if you do get that urge to remind the community about add-on reviews? The first step is not pressing Reply button. Rather, it should be waiting for the add-on release to go out so the release notice can be seen by people. This is the reason why I usually don’t reply to release announcements except to announce what will happen when it comes to add-on updates or the poster asked for specific feedback.

Still feel you need to remind the community about your add-ons? The next step is to go through the list archive and search for threads dealing with your add-on (ideally one thread per add-on or a collection of add-ons under a common theme). After you find it, write a reply to THAT thread, asking us about updates. People will try their best to answer you.

Second, please DO NOT make a person feel inferior by telling the community about a spoken language or other identity markers. Telling people that an add-on isn’t reviewed because the author speaks a specific language or two amounts to racism and classism, even if it was a joke. This is more prominent today because of the COVID-19 pandemic, as some groups around the world are fearful of such remarks that undermine who they are (as an Asian living in United States, I’m more sensitive to certain remarks).

The NVDA add-ons community is an international, multilingual community of volunteers working together to improve the lives of NVDA users with add-ons (I’ll address why I said it like this in a second). People come from different countries and backgrounds, speaks a variety of languages, brings diverse experiences with NVDA and Python, and developed many add-ons that are helping users across contexts. As such, it is not right for people to show racism and classism, especially language-based discrimination. Let us not show racism anymore.

Third, remind ourselves that, apart from NV Access people, we are all volunteers. Many add-on authors (some of them working for companies and organizations) volunteer their time to improve lives of NVDA users by writing add-ons. Some authors use time after studying to maintain add-ons. Add-on reviewers review add-ons in their spare time. Translators translate add-ons as volunteers.

Throughout the history of this community (which officially began in 2013), you may have noticed things such as review requests staying open for a while, add-ons not seeing timely updates, lack of translations in certain languages and what not. As much as the community wants to make these procedures predictable and efficient, it is far from that due to the very nature of who we are: volunteers. This is more so for authors and reviewers (also included are translators) as we need to balance add-ons work and life priorities. That doesn’t mean that authors and reviewers can neglect what we do in this community – ultimately, the question comes down to what am I supposed to do at this moment. Unless you are NV Access staff, I believe life priorities should take the front seat when conflicts arise (that’s why I wrote to Carter that I’ll do something about Text Information add-on this weekend; although I’m staying at home, I’m taking courses from Zoom University aka online courses from my college, so being a student is a priority in life).

To summarize, what I’m essentially saying is that I felt disappointed and angry, as the NVDA add-ons community may have forgotten who we are as a whole. And with recent events added to the mix, our collective forgetfulness increased our frustrations. Let us never forget who we are as we travel through uncertain times.

Thank you.

Cheers,

Joseph

hi.

i've merged master into stable

thanks.

On 5/5/20, Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:

Hello Beqa


Since you seem to have time these days, could you please do the
following regarding InstantTranslate:

* Update the strings to translate for translators. Indeed, translation
of this add-on has not been updated for many years, even if this add-on
is already in the translation system. For this, you need to merge master
into stable and ask to push your new stable branch to nvdaaddons'
InstantTranslate repo.

* Make a new release containing unpublished last commits (restore
language detection, new languages addition)) as well as new translation
when they will be available. For this, you will need to update your
stable branch from nvdaaddons' stable branch (containing future new
translations) and merge stable into master to get new translations in
the master branch.


Could you also tag the future releases in GIT so that we can follow more
easily releases in GIT?


If something is not clear or if you remain stuck somewhere, do not
hesitate to ask.

Thanks.

Cheers,


Cyrille

Hello Beqa


Since you seem to have time these days, could you please do the
following regarding InstantTranslate:

* Update the strings to translate for translators. Indeed, translation
of this add-on has not been updated for many years, even if this add-on
is already in the translation system. For this, you need to merge master
into stable and ask to push your new stable branch to nvdaaddons'
InstantTranslate repo.

* Make a new release containing unpublished last commits (restore
language detection, new languages addition)) as well as new translation
when they will be available. For this, you will need to update your
stable branch from nvdaaddons' stable branch (containing future new
translations) and merge stable into master to get new translations in
the master branch.


Could you also tag the future releases in GIT so that we can follow more
easily releases in GIT?


If something is not clear or if you remain stuck somewhere, do not
hesitate to ask.

Thanks.

Cheers,


Cyrille

Hi all,



Some important edits were made to community add-on template (source code:
https://github.com/nvdaaddons/addonTemplate), mostly dealing with
sconstruct
file:



* Custom versions and add-on documentation: previously when generating
add-on documentation from command line tools, a custom version specified
from command line would not be applied to add-on documentation. This has
been fixed.
* Add-on documentation: now generates HTML5 (credit: Noelia Martinez).



Also, some parts of add-on template will be subject to Flake8 tests/edits
(mostly sconstruct), and hopefully modernizing sconstruct in the process. I
don't expect add-ons to use the new sconstruct, but I highly encourage you
to update add-on source code based on latest happenings with the community
add-on template to add uniformity.

Cheers,

Joseph

Dear Everyone,
I would like to find out how forms mode is activated. The case is as follows:
1. NVDA's forms mode is set to manual activation.
2. I have a custom react combobox component, which is recognized as such.
3. Items are provided by aria-activedescendant association fom an
unordered list items.
4. When I scroll onto this component using arrow keys forms mode gets
activated automatically where it should be manual.
Any ideas what might be causing it? For example hint: focus event
attached to a incorrect HTML DOM node?
The structure of the component is as such:
<div role'combobox' aria-haspopup='listbox'
aria-activedescendant='ID_OF_ITEM' aria-owns='ID_OF_UL_CONTAINER'
aria-controls='ID_OF_UL_CONTAINER'>... </div>
<ul id='ID_OF_UL_CONTAINER' role='listbox'>
A number of items...
</ul>
Once the forms mode is activated, focus seems to betrapped. I can
escape out of this combobox using tabbing, but cannot do it with the
escape key or using NVDA's insert + space shortcut to get back
tobrowse mode.
Thanks for any feedback... Pawel

Digital signatures identify/authenticate you as the document signer and allow document recipients to verify that no one has modified the contents of the document since you signed it. Signing, Encrypting and reading will vary depending on the applications that are involved.
A Digital ID certificate is required to create a digital signature. The most secure Digital ID are issued by a trusted Certificate Authority. Some of these Digital ID’s are on tokens and other are files that are imported into trust stores on your system or application.
Note: Adobe Acrobat Reader DC is used for signing pdf files that application can be downloaded by visiting the Adobe Website here.
Note: If you cannot download this application due to firewall permissions or It has not been cleared within your organization  then you will need to do the needful and contact your companies IT team.
To sign a pdf document perform the following:
Step 1: Open or create your pdf in Adobe Acrobat
1. In Adobe Acrobat Reader open or create the PDF you would like to sign.
2. Click the Tools tab and then click under Certificates click Open.
Adobe_Acrobat_Reader_Tools__00…
3. A new section will be appended to the top of your document called Certificates. Click Digitally Sign.
4. Using your mouse, click and drag to draw an area where you would like the signature to appear. Once you finish dragging out the desired area, you will be taken to the next step in the signing process.
Note: In the example below I drew out a box area next to the Acmetek header (anywhere will do). Left mouse click > Drag a box > Release.
adobe_acrobat_reader_dc_certif…
5. In the Sign with a Digital window, select by clicking on the digital signing certificate you would like to use, then click Continue.
Note: If there are No digital signing certificates available then click Configure New Digital ID > Use a Digital ID from a file. This will require you to browse to your Digital ID pfx/p12 file in order to import it.
Note: If you are totally lost and have no idea what a pfx/p12 file is refer to How to Import A Digital ID, Email, or Code Signing Certificate Into A Windows System?
Adobe_Acrobat_Reader_Sign_with…
6. In the Sign as page of the wizard this is where you get to customize how your pretty Signature is going to look.
Note: If you click Create you can customize the signature by adding pictures, and selecting what is added to the signature from the information that is pulled from the Digital ID.
7. Click Sign.
Adobe_Digital_Signature_signin…
8. After you click Sign you should get a pup up window to save your newly signed pdf file.
9. After saving this file if you open it up you should now see your signature in the location you drew out for signing.
Adobe_reader_signed_pdf
Congrats you have just digitally signed your pdf file.
If you are unable to use these instructions for your server, Acmetek recommends that you contact either the vendor of your software or the organization that supports it.
Adobe Support
For more information refer to Adobe