https://bugs.documentfoundation.org/show_bug.cgi?id=141198

--- Comment #11 from Federico Gallo <[email protected]> ---
Hi.
I've been studying this report today to create a testcase (my first one) but I
found the following difficulties and I have some notes I would like to share:

1) Irrelevant or not, we should start by asking ourselves where that `Shift-F3`
shortcut came from. The shortcut is there, next to `Format`>`Text`>`Cycle Case`
but it is not in the documentation.
  - This is the documentation for LO 7.6 Writer:
https://help.libreoffice.org/latest/en-US/text/swriter/04/01020000.html?DbPAR=WRITER#bm_id3145763
  - And this is 6.2 (Writer too):
https://help.libreoffice.org/6.2/he/text/shared/04/01010000.html?DbPAR=SHARED#bm_id3149991
  - If you're wondering, here is the docs for OOo (it's not there either):
https://wiki.openoffice.org/wiki/Documentation/OOoAuthors_User_Manual/Writer_Guide/Shortcut_keys_for_OpenOffice.org_Writer

And it works, however when tracking is enabled things fall apart. But just
under certain circumstances, and that is when changes are made on changes that
have not been accepted or rejected. (See section 3)

2) Perhaps we are misinterpreting changes tracking functionality with
undo/redo. Personally I think I need to open the discussion to this before
suggesting a test case.
  - An author creates a document and saves an initial text ("This is the
initial text")
  - The document is saved, Track changes is then enabled, and the document is
saved again.
  - A different author opens the document, adds a change (capitalizes
"initial"), and saves the document.
  - So far no one has approved or rejected the proposed changes.
  - Note that at this point initial should be -initial-_Initial_, meaning
-initial- colored/struck-out lowercase, and _Initial_ colored/underlined.
  - A new author opens the document and adds changes to the word "initial" (to
uppercase) and saves the document.
  - Important note: There might be a disclaimer from the person opening this
Report (or any of you) but the change (apply uppercase to the word) should be
applied to the word, not to the word and its previous state.
  - The original author opens the document and see the proposed changes. The
expected result should be the following:

  This is the -initial-_-Initial-__INITIAL_ text

where 
-xxx- means colored/struck-out
_xxx_ means colored/underlined

  - Also, the information about the changes from the different authors should
be shown on the `Manage Changes` sidebar.

I would like to know your opinion to start with this. For the disclaimer in
particular (mentioned in the step by step) because that could lead to
no-errors-found but users could still be opening bug reports for this.

3) As mentioned in section 1 and 2, the issue is still happening when changes
are applied to marks of changes instead of the resulting changed word (which
has no errors, not in my screen at least).

I will attach the document I made as example and I will wait for your approval
on this to proceed with the testcase.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to