Wow, Zoltan,
That was a story.
Writing to TAM: While I do not argue with OWGuru, there are some cases when
you simply MUST write to spec files or forget the whole idea. I'll briefly
describe when we had to do it, and what we did:
As some of you may know

, JDEdwards writes all it's printable reports to
PDF. What most of you probably don't know is that Adobe DOES NOT support
Cyrillic characters in PDF, unless font is embedded. Acrobat Reader can be
fooled into using Cyrillic font, but it uses standard font spacing, which is
very different from Russian (the language I'm actually talking about). This
makes reports, which are printed using standard Arial font, very hard to
read. There are two possible solutions: either change report font to a
monospace font, or insert correct spacing info into PDF by a post-processor.
By the time we worked on solution, we have not considered the second option
(I never told I know how PDF is structured). Font override application is
only working for double-byte language.
At first we selected a list of reports we considered critical and had 2
consultants (junior, but precious still) go into each report and each
version of each report and change font. It took 3 days for less then 100
reports. And then we decided we need to do something. We've spent some time
examining related Central Objects tables, looking at them both in BLOB
fields and with UTB, experimented a little, and finally came up with a
program, which processes a pathcode for B7332 in less then half an hour. All
of programming took less then two days, and most of the time was spent
fixing different VB and VBA issues, and having the programmer accustomed to
Oracle and OneWorld. I can't describe the joy I felt when I say the program
working. Even the fact that we have to rerun it every now and then, because
Arial is leaking thru, did not spoil the joy.
A couple of tips for those, who have to do it: Don't be afraid, just be
careful and take your time. Use TAMMenus=Show and examine the BLOB contents
from two sides. In header files, at least some TAM structures are described
(for those who don't know, as I did not - BLOB is just storing a C
structure). Do some experimenting with simple reports/applications you
create specifically for this purpose, so you can easily test it. Do it first
in DEV or CRP.
And another tip, for those just curious: there are other interesting things
both in OneWorld and in outside world, explore those and don't mess with
specs.
Hope you'll find it usefull,
Vladimir Ponomarev
PS: If you ask me, if we had the problem completely solved - the answer
would be, NO. But it got better and we can live until SP 15, where they
promise to fix everything
PPS: I'm sorry, I'm not a programmer, but those of you, who need specifics,
can mail me off-list and I'll forward your mail to our developer.