|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | use different terms for Draw and Impress: "page" vs "slide" | ||
|---|---|---|---|
| Product: | documentation | Reporter: | IngridvdM |
| Component: | Online help | Assignee: | AOO issues mailing list <issues> |
| Status: | REOPENED --- | QA Contact: | |
| Severity: | Trivial | ||
| Priority: | P3 | CC: | issues, masaya.k, mseidel, rainerbielefeld_ooo_qa |
| Version: | 680m70 | ||
| Target Milestone: | AOO PleaseHelp | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://issues.apache.org/ooo/show_bug.cgi?id=124145 | ||
| Issue Type: | DEFECT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
| Issue Depends on: | 42865 | ||
| Issue Blocks: | |||
|
Description
IngridvdM
2005-01-17 16:07:57 UTC
please specify "future". When will the names for the Draw menu items be changed, for OOo 2.0 or later? The target for that change is OOo 2.0 see Issue 40806. changed text\simpress\00\00000402.xhp and text\simpress\01\02130000.xhp and text\simpress\01\04010000.xhp and text\simpress\00\00000404.xhp Change Prio failed Menu Edit - Delete Page has wrong format; no link Menu Insert: Slide still visible The 3 strings in the menu are targeted to be fixed with Issue 42865. This task it as risk to make it into the final as it depends on another issue. In my opinion it would be nevertheless better to have a correct help here. So what's the status now? The help text was changed before the menus were adjusted. The help was matching the menu entries. Now it does no more. ->UFI: *Never ever again* change the help for UI entries before you see the changes in the UI. How do we proceed with this one now? Check in master after hc680pb3 is integrated and either retarget to later or set to invalid. Holy mess. There is no mess. This change request was handled appropriately, although very very close to the documentation deadline. The problem is work overload on documentation in the few days before deadline (they all wait till the last days) and too long turnaround cycles to see the results of any changes in time. So if a change is not perfect on first try, there is no second chance until the next version. This should be addressed. The mess I refer to here is that the change request was made to TechPubs and then the change may not make it into the product. So we're one step ahead (as always). You're right, this must be addressed in context with the "document based on specs" paradigm. I didn't mean to blame one of /us/, of course ;-) -> FPE: You will also risk inconsistency between product and help, if you first make the changes in the product and afterwards in the help and documentation. The only way to guaranty consistency would be to do the help and documentation changes within the same CWS as the product fix. Maybe we should try such a process change. ->IHA: In general, I agree but usually documentation ought to follow implementation and not the other way round. There are still some problems to be overcome regarding the way we best implement help parallel to implementation. Sharing a CWS for feature and help would be one option but poses other issues, one of them being that the help is *big* and would be part of almost all feature CWSs and the majority of bugfix CWSs preparing the ground for conflicts. cannot be fixed for 2.0. retargeted The UI change will take place not before SO9/OOo3. Help files will be changed following the UI changes. Set target to later. *** Issue 52641 has been marked as a duplicate of this issue. *** *** Issue 53057 has been marked as a duplicate of this issue. *** Reset the assignee to the default "issues@openoffice.apache.org". |