Issue 83371 - find and replace/Searching for umlaut doesn't wrap around properly
Summary: find and replace/Searching for umlaut doesn't wrap around properly
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 2.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2007-11-06 14:45 UTC by ronnystandtke
Modified: 2013-02-07 22:05 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
the problematic file (222.00 KB, application/msword)
2007-11-06 14:46 UTC, ronnystandtke
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ronnystandtke 2007-11-06 14:45:34 UTC
I got a .doc file from my institute and noticed that rendering of some umlauts
is broken (see Bug#83370). So I pressed Ctrl+F and started searching for other
occurences of "ö".
Strangely, this worked only once. After the search hit the bottom and started
again from the top of the document I only got an error message that the string
was not found within the document.
I will attach the file.
Comment 1 ronnystandtke 2007-11-06 14:46:15 UTC
Created attachment 49463 [details]
the problematic file
Comment 2 ronnystandtke 2007-11-06 14:47:59 UTC
Another interesting observation: When running on Windows instead of Linux OOo
does render the umlaut fine but fails to find it even on the first try...
Comment 3 michael.ruess 2007-11-06 15:26:01 UTC
Reassigned to SBA.
Comment 4 lohmaier 2009-04-28 16:11:15 UTC
confirmed with OOo 3.0.1 - but only with "ö", "ä" for example wraps
around/starts search for ä at the beginning of the doc.

Searching for "ö" works as well again when you browse to the start of the document.



Comment 5 ronnystandtke 2010-05-17 13:33:00 UTC
I just tested with OOo v3.2. Rendering is fine now but, unfortunately, searching
is still broken as described in the initial report...
Comment 6 Raphael Bircher 2011-10-05 14:12:32 UTC
Too low priority. Set to P3