Open GoogleCodeExporter opened 9 years ago
problem is with zsaplink_installer...working on fix now
Original comment by ewherrm...@gmail.com
on 11 Oct 2006 at 1:22
I think the problem is in the main program, where the success messages after the
installation or export of a nugget or object are hard coded in the report.
My suggestion would be to create a plugin for message classes :-) and bring the
texts
there (that would also be easier for replacing paramters in the translation, if
the
position doesnt fit between the part strings that are actually used).
Original comment by kiefer.s...@googlemail.com
on 11 Oct 2006 at 5:31
Hi Sascha, yes you are correct, message class would be best as the status
messages
are currently hard coded in the program as English. Actually, John Patterson, a
developer for another company, is currently writing a plugin for message
classes.
Once he finishes this, we will be able to change our messages to use message
classes
and then utilize his plugin. He is the author of the SUDOKU application and is
using
SAPlink for distribution. For more info, check out his blog on SDN:
https://weblogs.sdn.sap.com/pub/wlg/4590
Original comment by ewherrm...@gmail.com
on 11 Oct 2006 at 10:25
OK, so I don't have to start writing the export plugin.
As soon as it's finished, I can take care of bringing the core program to
messages
and translate them...
Original comment by kiefer.s...@googlemail.com
on 12 Oct 2006 at 3:19
Hi there
I have written the plugin for Message Class and tested it in the following
systems
620 640 and 7.
I didnt know where to put the source so I attached it to this message.
Cheers
John Patterson
Original comment by patte...@gmail.com
on 13 Oct 2006 at 6:08
Attachments:
Original comment by ewherrm...@gmail.com
on 17 Apr 2007 at 6:21
Original comment by ewherrm...@gmail.com
on 17 Apr 2007 at 6:50
Original issue reported on code.google.com by
kiefer.s...@googlemail.com
on 10 Oct 2006 at 1:52