Apache OpenOffice (AOO) Bugzilla – Issue 59796
staroffice mentioned in help
Last modified: 2021-05-30 17:04:44 UTC
Help - Common topics - OpenOffice.org options - Text document - Compatibility contains following chapters: Use StarOffice 6.0/7 tab stop formatting Use StarOffice 6.0/7 line spacing Use StarOffice 6.0/7 object positioning Use StarOffice 6.0/7 text wrapping around objects In GUI there is variable %WRITERCOMPTIBILITYVERSION11 used instead, so in GUI we see "OpenOffice 1.1" in Tools - Options - Writer - Compatibility
.
The help doesn't know this variable. Suggested fix: (1) The variable must be handed over to the transformation style sheet, (2) the main_transform.xsl must be modified to evaluate it, and (3) the help text must be changed to use the variable. Andreas, I believe you need to do (1) I can do (2) Uwe, yours is (3) Would it make sense to have a complete list of all variables used in the office to see which ones we need to have in the help, too?
Obviously there is a need for a complete list of variables used in UI, plus the text they insert for the various versions of %PRODUCTNAME. And copy and paste should be used, to eliminate doubts about variables like %WRITERCOMPTIBILITYVERSION11 which may or may not need an A character inside. Can change the text only when I get such a list and/or a confirmation on the correct name. Change makes sense only when (1) and (2) are implemented.
please take over
@abi: Did you implement (1)?
as "abi" is no longer available, may be this is for "ab" to implement step 1 of the list?
changing owner
STARTED
No resources left for 3.0 -> 3.x
Reset assigne to the default "issues@openoffice.apache.org".
We have 8 strings with this variable. Localization: https://github.com/apache/openoffice/blob/trunk/main/sw/source/ui/config/optcomp.src https://github.com/apache/openoffice/blob/trunk/main/helpcontent2/source/text/shared/optionen/01041000.xhp Anybody knows if %WRITERCOMPTIBILITYVERSION11 must be replaced or reintroduce?
Fixed now in trunk, AOO42X and AOO41X. *** This issue has been marked as a duplicate of issue 122765 ***