AW: Workitem Text Translation

[Schmidinger, Heinz (Unaxis IT BZ)]

Hi Marc,
as Jocely explained, you have to use Tx SE63.
 
The disadvantage of translation line by line can be rduced with this
workaround.
 
If you have only one character in another languge, you get the =
possibility
in PFTC to maintain all creted language-dependet texts directly.
 
maybe it helps.
 
regards
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Mark Pyc
Gesendet am: Donnerstag, 26. August 2004 18:26
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Workitem Text Translation
 
G'day Wugers,
 
Hopefully a few very simple queries dealing with Workitem text
translations.
 
The long text has it own in built translation function in PFTC or
equivalent, so thats fine.
 
It's possible to use Extras > Translations > Translations to translate =
the
technical definition so that people could read the log in their own
language, but that's not what I'm after.
 
What I wanna know, what I really really wanna know is, is it possible =
to
maintain a WI text in another language other than by logging on in that
language and changing it at the task?
 
What can be maintained via SE63? The Bible does refer to using it, and =
does
refer to needing to perform 'Compare Texts with Transport Version' to =
get
the texts loaded into the development version. My question here is what =
are
you maintaining in SE63 and how do you find it to maintain it? I'm on a =
WAS
620 post SP25 system which has a Unicode compliant version of SE63 if =
that
makes a difference.
 
Have fun,
Mark