Extension AltSearch - bugs and requests

English
#17

Some improvements In GIthub

I think all the code of the extension must be in a subdirectory.

So in the root directory you can put some utilities like the Readme.md, the update information, the compiled extension and a batch to compress the extension.

(Look at my extension on github) GitHub - Bantoniof/LibreOffice-SanityCheck: ExtensiĂłn para LibreOffice Writer

#18

@fpy marvellous work, thanks for manual with printscreens! But you are too much fast for me in these days :slight_smile:. I will try it probably next week, I really want to finish the translation of comments. Module AltSearch is translated that is about 30%.

#19

sure, no hurry.

you’ve noticed @bantoniof did already a few translations : 1.4.3b from @bantoniof by gitxpy · Pull Request #4 · gitxpy/libreoffice-alt-search · GitHub

fair.
hope some unit tests at some point;
also, do you know if there’s a batch upload to extensions.libreoffice.org ?

anyhow, let’s first have @KamilLanda up to speed colfortably, then try to move forward.

#20
  • The translations I’ve made was for the localization in Spanis that wasn’t update to v1.4.2
  • I think that @KamilLanda want to translate the code comments to English, so the code can be more comprensible.

I Don’t know, I suspect not it is possible because you must log in the extensions page to publish the extension. (But you can do the extension updatable from Github)

1 Like
#21

I already added Spanish translations from @bantoniof to version I make

1 Like
#33

Yes, Now I found where is my confussion.

  • The previous license was LGPL
  • We changed the license to CCO
  • When publissing in Github, GIthub added an Apache v2 license file with name LICENSE (can see in branchs) And in the organization I put this file in the “registration” subdir.

So


  • In the help the link to the license must be to CCO
  • The file /registration/license.txt must contain the real CCO license.
#34

In version 1.4.2 and 1.5.2, the following situation arises: I want to clean up several paragraphs in a text (copied from a PDF, contains paragraph breaks after each line) by replacing the superfluous paragraph marks with spaces. I would select the area and call up Altsearch with the command replace (\p - space). Once this is done, I would click on OK, select the next area and click on Replace again. Previously, this worked repeatedly without closing Altsearch. Now instead the cursor jumps back to the previously edited selection, where there is nothing left to replace. I have to close Altsearch and reopen it again to replace within the next selection. This was not necessary before. Is it possible to reprogram it so that after completing the replacement and clicking OK, a new area can be selected and edited? Thank you!

#35

not sure how long ago it was, and if it’s still working with recent versions of LO.

could you please follow up opening an issue there → libreoffice-alt-search/issues/new

#36

It seems like AltSearch bug #134 and unfortunately I don’t know how to fix it :frowning:
But I tried AltSearch 1.5.2.0 in older Libre 6.4.7.2 and it was ok, so the cause is some change or bug in newer versions of Libre?

#37

Hi fpy,

Thanx, typo, sorry, my bad: Version 1.4.2. I corrected it.

I didn’t find libreoffice-alt-search/issues/new. Is there a link?

I put it on GitHub: Kind regardds, hjm

#22

Here is new version
altsearch_150beta1.oxt.RENAMED.ODT (762.8 kB)
The description is in module changes

@fpy or @bantoniof I haven’t own internet :frowning: so I must periodically “travel” to my neighbourgh’s wifi and do the operations only with touchpad, that really isn’t comfortable for more Drag&Drop operations. So please could you also take from @htietze the administration of Libre Extension site? Thanks.

1 Like
#23

Hellow @KamilLanda, Thanks a lot for your translation work

Testing the 150beta I found a bug:

Searching for char Style “Destacado” in Spanish localized version ( Realname = Emphasis)
I get the incorrect property value error in line 2842 (Function getRealStyleName)

(The 143beta version was ok )

Windows 10, L.O. 25.2.3.2

#24

Ok fixed, 150beta1 up

#25

I have replaced the function getRealStyleName with the old function (143b) and the search is ok.

But now, the Replace with another Char Style causes the not established object variable error
(in the same line)

  • May be different forms of call to function in search / replace?
#26

In 143 the function getRealStyleName(
) had 1st parameter the object but in 150 is 1st parameter string!
It was easier to change the parameter to string than create new variable with next object in other calling that was with \A in Replace and not only \C.
But I forgot to change it in all occurences of getRealStyleName in 150.


But the uploaded 150beta1 is functional for me:

img
img1852×811 91.2 KB

#27

I had not realized that you had edited the message and uploaded the new version. (beta1).

  • Tested and is Ok .

  • Thank you very much You are very efficient and fast

1 Like
#28

ok. so, catching up with commits, the first was HUGE !! :sweat_smile:
150beta1 is more reasonable / readable :wink:

image
image1277×576 168 KB

→ Commits · gitxpy/libreoffice-alt-search · GitHub

1 Like
#29

@fpy you can do really small fix now, there stayed cs comment in Common.xba :slight_smile:

one-cs-comment
one-cs-comment1554×627 82.6 KB

:

#30

@fpy please will you also take over the administration of Extension site AltSearch » Libreoffice Extensions ?

#31

done.
image

can’t wait you directly join the github vibe :wink:

the beta is available from latest git main :

image
image1083×310 57 KB

1 Like

Impressum (Legal Info) | DatenschutzerklĂ€rung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.