|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Update of AutoText dialog too slow | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Writer | Reporter: | ingenstans | ||||
| Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
| Status: | ACCEPTED --- | QA Contact: | |||||
| Severity: | Trivial | ||||||
| Priority: | P4 | CC: | christophe.badina, issues | ||||
| Version: | 644 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 2000 | ||||||
| Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
| Developer Difficulty: | --- | ||||||
| Attachments: |
|
||||||
|
Description
ingenstans
2003-03-11 11:33:12 UTC
Created attachment 5050 [details]
MS Word template where autotext import fails
attachment created: the MS word template fro which I was trying to import some autotext. MRUs area. Assigned new target Milestone. That's all working correctly. Word's Autotext do not have a "Shortcut"-Feature. They are all just stored by their name. Writer's Autotext import uses their names as names (sounds logical for me) and the shortcuts for Writer are generated automatically. BTW: I do not know why you say "horrendously broken". In your opinion, shortcut/names are mixed up. But it works, when inserting. Closed, is not a bug. The reason I said it was "very broken" was partly that autotext is grindingly slow; on a 400mhz machine it can take five seconds to insert a text after pressing "Run autotext". Quicker to write it. But I still think that the import from Word is broken: here's why. AS you observed, Word does not have separate names and short cuts for autotexts. But what Word calls "names" are what OOo calls "short cuts": they are used by typing the "name" and then pressing the completion key. That's what the finger memory expects, and that's what's broken in OOo, where you're expected to type the name and then press "return" as if it was a normal word completion. What I would expcet the import function to do is to assign Word's "names" to OOo "short cuts", and then to generate and assign OOo "names" automatically. At present it works the other way round, and that is, I think, a mistake. It only affects the people who import large Word autotext libraries, but they are the people who need them, and are used to using them in one particular (Word's) way. So I don't think it's a successful import if it at the end of it the autotexts have to be accessed in an entirely different way, when that could easily be avoided by assigning Word "names" to OOo "short cuts". Reclose the issue if you think I'm wrong. And I'm not sure if it is not an enhancement rather than a defect. But I did want to make clear my objection and the reasons for it. MRU->CMC: Andrew is partly right. The shortcuts should remain in a way. The only thing i could ima gine is, that we do not generate shortcuts automatically from the names and also take the name from Words Autotext as shortcut. What do you think about it? I'll give it a try :-) cmc->mmaher: One for you to try: The glossary import code is in ww8/ww8glsy.cxx. From the menus edit->autotext->autotext->import to launch an import MM: Putback a fix so that Word's autotext name is imported as both the shortcut and the name in StarWriter. The performance issue is a UI problem and after some investigation with truetime and discussion with Oliver am reassigning to OS. Changed prio to 4 Changed summary, was: import autotext from word very broken according to the announcement on releases (http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue will be re-targeted to OOo Later. Reset assigne to the default "issues@openoffice.apache.org". |