[sw-issues] [Issue 47709] New - compose alt characters different from normal
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=47709 Issue #:|47709 Summary:|compose alt characters different from normal Component:|Word processor Version:|OOo 2.0 Beta Platform:|PC URL:| OS/Version:|Linux Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|editing Assigned to:|mru Reported by:|polbrian --- Additional comments from [EMAIL PROTECTED] Tue Apr 19 00:46:18 -0700 2005 --- OOO 2.0 is great, but... Typing [compose . alt+key . character] (for example to produce a (atilde) does not work in ooo2.0 beta as in the other applications. Actually, you must type alt, then add compose, then the diacritical key, then the key. I don't use ooo exclusively; I want consistency. (I would not mind doing it the Mac way or the Windows way, though I expect to do it the Linux way as ooo 1 did, even if it requires more typing). - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 47710] New - rtf loses styles name
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=47710 Issue #:|47710 Summary:|rtf loses styles name Component:|Word processor Version:|OOo 2.0 Beta Platform:|PC URL:| OS/Version:|Linux Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|formatting Assigned to:|mru Reported by:|polbrian --- Additional comments from [EMAIL PROTECTED] Tue Apr 19 00:52:23 -0700 2005 --- Opened a .rtf document created by MS Word 5.0 for Macintosh. *Nearly all* the formatting stood (see other postings). Could edit it, and on saving, ooo 2.0 did not show alert, and recorded in that same format. That's great. Opening this same document for another session, the custom style names were replaced by machine generated stuff: WW-1 WW-12 WW-123 etc. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 47709] compose alt characters different from normal
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=47709 --- Additional comments from [EMAIL PROTECTED] Tue Apr 19 00:55:01 -0700 2005 --- System: Suse Linux 9.0 (updated) on P4 3GHz desktop - Menu key as COMPOSE key. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sw-issues] [Issue 47750] New - HTML editor
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=47750 Issue #:|47750 Summary:|HTML editor Component:|Word processor Version:|OOo 2.0 Beta Platform:|PC URL:| OS/Version:|Linux Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|editing Assigned to:|mru Reported by:|polbrian --- Additional comments from [EMAIL PROTECTED] Tue Apr 19 06:25:10 -0700 2005 --- I am growing accustomed to type directly in HTML 4 or XHTML, and I have definite ideas over what my prefered HTML editor would look like. It would be same as ooo 2, except: 1/ entering a style name like ul.li.myclass results in a css .myclass class style definition, and the element to which I applied the style is coded li class=myclass.../li within the relevant ul element. 2/ likewise a dl.dt.moreclass#particular style applies to dt class=moreclass id=particular within dl 3/ the style dialog, in html, reflects the css definitions, with 4/ an option to have this style defined either on separate stylesheet or in the head element. 5/ text styles that are not coded using styles have HTML-3 type coding, such as p align=centerfont size=3b .../b/font/p and the like; that's about how it's done now. 6/ in Code View mode, there should be some basic debugging tools, such as, when the cursor is over an opening tag, highlight the closing tag (and vice versa) like editors do for brackets. 7/ there should be an ID list, and the program should alert the user on his trying to enter a duplicate id or to paste html code which provokes an id conflict. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
