Shahnawaz,

I did some testing and It looks like the Direct PDF does not support the <:pdfs;NOTE...> syntax.
My test file came out without notes when using Direct PDF with the pdfmark option set, but came out with notes when going through the 'PS to PDF file using distiller' route.

From reading the xyPDF manual it is not entirely clear to me whether this is a bug or simply not supported.
The manual speaks about supporting the <:pdfs> and <:pdfe> constructs in order to build bookmark and annotations the old fashioned way.
The manual is also very clear that the <:pdfs;GEN> macros are not supported.
But it is not clear what happens to all the other <:pdfs> and <:pdfe> macros.
(hopefully SDL engineering will tune in here with the correct answer...)

But anyhow even if this is a bug, you will have to open a support ticket and wait for the fix to come.
And of course you do not have the time to wait as you want a solution now

The easy solution is to not use the Direct PDF option but go through the PS to PDF file route.

But there is also an alternate solution. Here is what you can do.
I am assuming since you are still using the <:pdfs> and <:pdfe> macros that this is a job using the classic IF/XX setup but hopefully it is an XML job.
If that is the case, then the solution is to simply create an extra css file that will only contain the necessary pdfmark things but using the CSS syntax.
My test division was using the style 'xybase2'.
I create a CSS file called xybase2.css and in that file I just put:

@import url('xpp.css');

note {
-xpp-pdf-annotation: "type={note} text={text as defined in CSS}";
}

and when I printed this with Direct PDF and -pdfmark all was well and wherever the element note was sitting on the page I did get a PDF note.

Hope this helps...

Shahnawaz,

I did some testing and It looks like the Direct PDF does not support the <:pdfs;NOTE...> syntax.
My test file came out without notes when using Direct PDF with the pdfmark option set, but came out with notes when going through the 'PS to PDF file using distiller' route.

From reading the xyPDF manual it is not entirely clear to me whether this is a bug or simply not supported.
The manual speaks about supporting the <:pdfs> and <:pdfe> constructs in order to build bookmark and annotations the old fashioned way.
The manual is also very clear that the <:pdfs;GEN> macros are not supported.
But it is not clear what happens to all the other <:pdfs> and <:pdfe> macros.
(hopefully SDL engineering will tune in here with the correct answer...)

But anyhow even if this is a bug, you will have to open a support ticket and wait for the fix to come.
And of course you do not have the time to wait as you want a solution now

The easy solution is to not use the Direct PDF option but go through the PS to PDF file route.

But there is also an alternate solution. Here is what you can do.
I am assuming since you are still using the <:pdfs> and <:pdfe> macros that this is a job using the classic IF/XX setup but hopefully it is an XML job.
If that is the case, then the solution is to simply create an extra css file that will only contain the necessary pdfmark things but using the CSS syntax.
My test division was using the style 'xybase2'.
I create a CSS file called xybase2.css and in that file I just put:

@import url('xpp.css');

note {
-xpp-pdf-annotation: "type={note} text={text as defined in CSS}";
}

and when I printed this with Direct PDF and -pdfmark all was well and wherever the element note was sitting on the page I did get a PDF note.

Hope this helps...

And if you want the text to be variable, you will have to stick it into an attribute (e.g. @notetext) on the element <note> and in the CSS define note as:

note {
-xpp-pdf-annotation: "type={note} text={attr(notetext)}";
}

Thanks Bart for the quick response. It is really helpful for now.