USING "SÊARCH" & "FIND ALL", IS PROBLÊMATHIC,
IT DIS‑AP‑PÊARS AFTËR ÔNË EDIT,
AND IF WE RE‑ACTI‑VATHE IT,
WE GET AT START OF DOCU‑MÊNTH,
AND IF I HAVE TO CHANGE SH BY Ʃ OR TH BY Θ.
TO RE‑MOVE H & HN DE‑STRUC‑TI‑VE COM‑BINA‑TI‑ÔN :
HAN, HEN, HON, HUN, हन ههن هنن
WHO ARE CON‑FUS‑ING, AND NÊZHA‑TIVE...
ÊNGËL‑IS BASIC SCRI‑PTH, WITH‑OUT AC‑CÊNTH & NASAL... LIKE VASHA‑PRÊNSË.
BE‑TWEEN EPSILON ه HÊTA ح
OMICRO ع ÔMÉGA غ.
WITH BBAD RE‑SHULTHË UN‑DER‑STAND‑ING !
What do you mean by "one edit"?
Is there a reason you are not using Find & replace, as you appear to want to do editing?
I can't use search & replace be‑cause some should not get chang‑ed (like de‑fini‑ti‑ôn) of the com‑posite language that I'm creat‑ing...
I mean by one edit, one change in high‑light‑ed text. After change the high‑light dis‑ap‑pear, and we need to click again "FIND ALL", but we get at start of document and it is not practical.
(In reply to nemzag from comment #2)
> I can't use search & replace be‑cause some should not get chang‑ed (like
> de‑fini‑ti‑ôn) of the com‑posite language that I'm creat‑ing...
But you don't have to replace all of them.. you can skip what you want to preserve by clicking Find next.
Yes, we can, but still, the pro‑blem re‑main, I don't think that mak‑ing a change, should ën‑high‑light the sêarch, and re‑acti‑vat‑ing the "find all" should not re‑put you at start of docu‑mênth.
is still this issue reproducible under latest LibO 188.8.131.52?
please use normal english to reply and provide a better description of the bug so it's easier to understand what you exactly mean... It's hard to comprehend the original description.
status NEEDINFO until then.
revert to UNCONFIRMED if bug is still present and WORKSFORME if bug is gone
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker