Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 22 May 2017, 13:53
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Filesystem
Findnrun 2.4.0 - a progressive finder - updated 2016-09-06
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 3 [38 Posts]   Goto page: 1, 2, 3 Next
Author Message
step

Joined: 04 May 2012
Posts: 832

PostPosted: Sun 24 Jan 2016, 06:31    Post subject:  Findnrun 2.4.0 - a progressive finder - updated 2016-09-06
Subject description: Find applications and more
 

Latest version 2.4.0 released 6 September 2016

Findnrun version 2.4.0 is a recommended upgrade for all users.
Release highlights: The main window displays more configuration settings. Open the configuration file for editing directly from the main window. Symbolic links to .desktop files are supported (thanks SFR). Updated Italian translation (thanks xanad).

Upgrading

From version 2.2.0 - Please edit your existing configuration file[/b]. This is explained in the 2.3.0 release announcement page.

From earlier versions - Please edit your existing configuration file[/b] to run this version. This is explained in the release announcement page.

Download .pet and .txt packages

Full documentation in the project page on Github.

Findrun forked from the earlier Find'N'Run project at version 1.9.0 in May 2015. >old thread

Call for translators, please! See the third post in this thread.







Old Release Announcements

Version 2.3.0 released 1 August 2016
Findnrun version 2.3.0 is a recommended upgrade for all users.
Release highlights: Find applications installed by `wine`. Update Italian translation.

Version 2.2.0 released 2016-06-13
Findnrun version 2.2.0 is a recommended upgrade for all users.
Release highlights: New features, a new plugin, and some bugs fixes.

Version 2.1.1 Released 2015-04-25
Findnrun version 2.1.1 adds German and Italian translations, and fixes some minor issues. Recommended upgrade for all users.

Version 2.1.0 Released 2015-03-11
Findnrun version 2.1.0 is a bug-fix, compatibility and documentation release. Recommended upgrade for all users.

Version 2.0.0 Released 2015-01-24
Findnrun version 2.0.0 is a major new release. Main new features since version 1.10.6 include plugin support, hotkeys, improved icon GTK compatibility, faster search, and many minor improvements and bug fixes. Significant new plugins include the Shell Completion bundled plugin, and the Filmstrip demo plugin.

Last edit: Tue 26 Apr 2016, 16:31 All times are UTC - 4

_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus

Last edited by step on Tue 06 Sep 2016, 17:14; edited 12 times in total
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 832

PostPosted: Sun 24 Jan 2016, 06:31    Post subject:  

Reserved
_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 832

PostPosted: Sun 24 Jan 2016, 06:31    Post subject:  

This post is for translators

Version 2.1.0 significantly improves the translation kit. Reading the tutorial is recommended. Feedback is welcome.

Tutorial: Translations Demystified - explains what and how to translate Findnrun. Required reading for all translators, beginners and experts alike.

Some new things that need your attention:


  • When you start translating please let me know, so I can (1) keep you better informed of late-breaking news concerning translations, and (2) update the translation status at the bottom of this post.

  • The name "Find'N'Run" disappears from the script and documentation - except when it refers to the earlier script by FSR and L18L.
    Now please consistently use "Findnrun" - as you can see in the updated markdown documentation.

  • The tag line "Find and run applications very quickly" equally disappears from the script and .desktop file. The new tag line "Find applications and more" is a compromise between what we had before and my view of Findnrun as a "progressive finder" extensible to different data types by means of plugins. I kept the reference to "applications" because I reckon that most people will care for that one feature.

  • You really need to use the reference .pot template file, which is built using this script.

  • HTML documentation is discontinued. L18L's posts >1, >2 stimulated a transition to markdown format. This project is a testbed for mdview, a tiny but powerful markdown viewer that comes standard with Fatdog64-701, and is also available as a Woof-CE build recipe.

  • Until bugfixes are backported, you need to download and use the custom mdview version available from Findnrun's download page. See the Tutorial for instructions.



Translating Help Files

As I mentioned I hope for at least some of the markdown documentation to be translated.
Since the target is the end-user, the goal is to translate all end-user help files, which are:
CREDITS.md
hotkey.md
index.md
install.md
install-require.md
issues.md
plugin-list.md
plugin.md
preference.md
running.md
screenshots.md

The reference .pot file combines all window and dialog messages with the text extracted from the above list of .md files. Other .md files have been excluded. So, translating the pot text set is all that's needed.

Q: Is mdview available for your puppy OS?
A: Fatdog64-702 comes with mdview built-in and also as a gslapt package. For other puppies I know that Woof-CE includes an mdview build recipe but I don't know which puppies actually build it. Unofficial 32- and 64-bit builds can be downloaded from the findnrun release page. Those builds are meant for translators and include some necessary patches. End users should instead install an official mdview version >= 2016.04.26.

Translation Status

I have "volunteered" the names of all previous translators. Feel absolutely free to turn this incredible offer down if you can't help. Smile

* Chinese, 1.6.10, icake
* French, 1.6.10, ASRI
* German, 2.0.0, L18L
* Italian, 2.2.0, xanad
* Spanish, 1.6.10, Nelson Morales

Last edit: Tue 24 May 2016, 12:54 All times are UTC - 4

_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus

Last edited by step on Tue 24 May 2016, 12:55; edited 7 times in total
Back to top
View user's profile Send private message 
SFR


Joined: 26 Oct 2011
Posts: 1592

PostPosted: Sun 24 Jan 2016, 16:02    Post subject:    

Hey Step

Glad to see FNR is evolving. Smile

Greetings!

_________________
[O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource
Omnia mea mecum porto.
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 832

PostPosted: Sun 24 Jan 2016, 17:58    Post subject:  

Thanks SFR, I stand on the shoulders of giants Smile
_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 3368
Location: www.eussenheim.de/

PostPosted: Wed 27 Jan 2016, 12:44    Post subject:  

step wrote:
@L18L I don't know if the findnrun script is ready to show translated markdown or if I need to change it. Can you please advise me?

Append messages from .md files to your findnrun.pot:
Code:
cd /usr/share/doc/findnrun; for f in $(ls *.md); do [ "$f" != "TRANSLATING.md" ] && mdview --po $f >> bla ; done; msguniq bla >> /usr/share/doc/nls/findnrun/findnrun.pot; rm bla

Note
- excluded TRANSLATING because of some errors (and translators translate from English thus no translation)
-No
%%textdomain findnrun
in .md file necessary

- Partially translated using momanager see screeny

This answers your question: scripts are ready to run translations.
doc_findnrun.png
 Description   
 Filesize   31.87 KB
 Viewed   626 Time(s)

doc_findnrun.png

Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 3368
Location: www.eussenheim.de/

PostPosted: Thu 28 Jan 2016, 07:08    Post subject:  

@step
my post of yesterday was a shot too quick.
Scripts are ready to run translations but I did not care about your detailled request.

The usual way to create a pot file from several source files is using xgettext parameter --files-from=<file>

Thus, for mdview we should use also a file:
Code:
cd /usr/share/doc/findnrun
echo "hotkey.md index.md install.md issues.md no-help.md plugin.md preference.md running.md CREDITS.md examples/filmstrip/README.md" > translate

Create .pot file:
Re-create your original -pot file using xgettext; then run
Code:
cd /usr/share/doc/findnrun; for f in $(cat translate); do mdview --po $f >> bla ; done; msguniq bla >> /usr/share/doc/nls/findnrun/findnrun.pot; rm bla


Looking into multi-field.tap.sh,
why TEXTDOMAIN="findnrun-plugin-multi" ?
I would use one TEXTDOMAIN for all.
Re-create your pot file using xgettext <list of files>

ALTERNATIVELY:
Let me know if you want to use the automatic (puppy momanager) solution for dynamically creating pot file.
- Insert %%textdomain findnrun in each .md file that can be translated
- Use export TEXTDOMAIN=findnrun in the scripts
- Do not distribute any findnrun.pot, it will be created dynamically
The only thing I would have to add to momanger is: make use of xgettext parameter -c
and momanager will do all the work. Cool


LICENSE.md
Why not just a link to one of http://www.gnu.org/licenses/
and translators can additionally link to an existing unofficial translation from
http://www.gnu.org/licenses/translations.html if available.

Other notes might follow when translation starts ....
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 832

PostPosted: Thu 28 Jan 2016, 09:06    Post subject:  

L18L wrote:
@step
my post of yesterday was a shot too quick.
Scripts are ready to run translations but I did not care about your detailled request.

Thanks for your answers! I'm consolidating them in a script that creates the .pot file. I'll post about it when it's done.

Quote:

Looking into multi-field.tap.sh,
why TEXTDOMAIN="findnrun-plugin-multi" ?
I would use one TEXTDOMAIN for all.
Re-create your pot file using xgettext <list of files>

No, I want separate TEXTDOMAINs because plugin development is separate from findnrun. This way a plugin developer has all the freedom to localize the plugin the way he wants, and the findnrun development/localization track isn't encumbered.
Findnrun automatically uses gettext from a plugin TEXTDOMAIN as long as the text domain name follows the rule "findnrun-plugin-"<plugin name>. Currently, this is used to show translated plugin titles in the status bar and for nothing else. Finally, plugins can load gettext messages from their own TEXT domain, it's their option.

Quote:

ALTERNATIVELY:
Let me know if you want to use the automatic (puppy momanager) solution for dynamically creating pot file.

Thanks for the offer, but not now I think. I prefer to get a stable i18n release cycle before I start changing tools again.

Quote:

LICENSE.md
Why not just a link to one of http://www.gnu.org/licenses/
and translators can additionally link to an existing unofficial translation from
http://www.gnu.org/licenses/translations.html if available.

Good idea. But the license terms themselves say that a license file must be included with the software. Providing just the link to an online copy of the license doesn't meet the terms. Can't the translator simply replace the English license text with the corresponding translation from http://www.gnu.org/licenses/translations.html, if available?

Quote:
Other notes might follow when translation starts ....
When you do start the translation let me know and I'll update the 'translation status' post.
Thanks for your feedback and help.

_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 1923
Location: Germany

PostPosted: Thu 28 Jan 2016, 15:35    Post subject:  

Hi.

I have tried version 2.0.0, though I couldn't let it search for anything else than .desktop files.

How does all the other stuff work (Images, Filmstrips etc.)?
Any additions needed?
Any Guide available to set it up?

Thanks

_________________
RSH

In Deutschland bekommt jeder Depp Asyl, sogar BW-Soldaten, weil in den Behörden die absolut größten Deppen sitzen. Mathelehrer Hungerland: wer ungeeignet scheint, für das Fach-Abi, der bewerbe sich schnell bei einer Behörde!
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 832

PostPosted: Thu 28 Jan 2016, 17:14    Post subject:  

@RSH - You should at least be able to search for shell commands. After findnrun starts and shows desktop applications, press F3 - it should change the list to shell commands. If it doesn't then we need to troubleshoot:
1. What puppy version are you running on?
2. Do you or did you have another version of findnrun installed? Which version?
3. Attach contents of your ~/.findnrunrc file.

Filmstrip documentation is located in /usr/share/doc/findnrun/examples/filmstrip/README.md. Open with mdview (preferred) or a text editor.
Here's a link to the online version of Filmstrip README.md

Findnrun user documentation is located in /usr/share/doc/findnrun/. Open by pressing F1 in findnrun main window, or open file index.md directly with mdview or a text editor.

Thanks for trying, keep feedback coming.

_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 3368
Location: www.eussenheim.de/

PostPosted: Fri 29 Jan 2016, 06:24    Post subject:  

step wrote:
When you do start the translation let me know and I'll update the 'translation status' post.

started...
Code:
#: /usr/share/doc/findnrun/index.md:52
msgid "[2] Markdown files can be confortably read as plain text files. To browse markdown files install the `mdview` package."

This comfort can apply only for English as the plain text files are and stay English only.
The comfort of translation (if exists) can be gotten only by using mdview.

Quote:
But the license terms themselves say that a license file must be included with the software. Providing just the link to an online copy of the license doesn't meet the terms. Can't the translator simply replace the English license text with the corresponding translation from http://www.gnu.org/licenses/translations.html, if available?

The license tells another story about translations
Suggest to embed the content of LICENSE.md into
%%nopot yes
and
%%nopot no
to prevent it from being gettexted.
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 832

PostPosted: Fri 29 Jan 2016, 07:59    Post subject:  

L18L wrote:
step wrote:
When you do start the translation let me know and I'll update the 'translation status' post.

started...
OK, thanks, post updated.

Quote:

Code:
#: /usr/share/doc/findnrun/index.md:52
msgid "[2] Markdown files can be confortably read as plain text files. To browse markdown files install the `mdview` package."

This comfort can apply only for English as the plain text files are and stay English only.
The comfort of translation (if exists) can be gotten only by using mdview.

Good points. I will change those sentences in the markdown files. So non-English readers have one additional motivation for installing mdview! Smile

Quote:

Suggest to embed the content of LICENSE.md into
%%nopot yes
and
%%nopot no
to prevent it from being gettexted.

Actually I was just going NOT to include the contents of LICENSE.md into findnrun.pot - but I will still add those fences to the .md file, as you recommend.

I am going to push a few i18n updates to github today. Including the unified .pot file. I hope that won't upset your translation too much. Thanks for your help!

_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 3368
Location: www.eussenheim.de/

PostPosted: Fri 29 Jan 2016, 09:33    Post subject: Findnrun 2.0.0 - a progressive finder
Subject description: updates and translations
 

step wrote:
I am going to push a few i18n updates to github today. Including the unified .pot file. I hope that won't upset your translation too much.

No worries, updates are part of life.
Translations of updates are not lost, they are mostly marked fuzzy.
You have more work with updating your static findrun.pot.
Back to top
View user's profile Send private message 
step

Joined: 04 May 2012
Posts: 832

PostPosted: Fri 29 Jan 2016, 11:10    Post subject: Re: Findnrun 2.0.0 - a progressive finder
Subject description: updates and translations
 

L18L wrote:

No worries, updates are part of life.

You have more work with updating your static findrun.pot.

Panta rei! I build findnrun.pot with this script.

I just uploaded the updated version.

_________________
Fatdog64-710|+Packages|Findnrun|+forum|gtkmenuplus
Back to top
View user's profile Send private message 
L18L

Joined: 19 Jun 2010
Posts: 3368
Location: www.eussenheim.de/

PostPosted: Fri 29 Jan 2016, 13:03    Post subject: Re: Findnrun 2.0.0 - a progressive finder
Subject description: updates and translations
 

step wrote:
I build findnrun.pot with this script.

Code:
msguniq --no-wrap --no-location "${FPOT}.tmp"

I (and all translators) do need locations.
- see context
- see what is no more actual (no context - no more needed)

please use headers ## and ### not just ** **
ex:
35 msgid "**Packages**"
381 msgid "Packages"

if ### packages there is one translation only.


Let the flow continue.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 3 [38 Posts]   Goto page: 1, 2, 3 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Filesystem
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0844s ][ Queries: 14 (0.0063s) ][ GZIP on ]