official (momanager) language packs
- ASRI éducation
- Posts: 3197
- Joined: Sat 09 May 2009, 12:10
- Location: France
- Contact:
woof-ce-testing: pdesktop translation with momanager
I just created a Puppy Precise version based on the latest version of woof-ce-testing (20150611).
My problem: I can not translate the last Zigbert interfaces.
momanager does not show me the files to translate.
An example: how do you translate pdesktop Apps?
Thank you in advance for your advice.
My problem: I can not translate the last Zigbert interfaces.
momanager does not show me the files to translate.
An example: how do you translate pdesktop Apps?
Thank you in advance for your advice.
Projet ASRI éducation => [url=http://asri-education.org/]Association[/url] | [url=http://forum.asri-education.org/]Forum[/url] | [url=http://dl01.asri-education.org/]Dépôt[/url] | [url=http://kids.asri-education.org/]Espace kids[/url]
- xanad
- Posts: 400
- Joined: Fri 28 Feb 2014, 14:56
- Location: 2 locations: MonteRosa Alp and Milano
- Contact:
Re: woof-ce-testing: pdesktop translation with momanager
pdesktop has no the 'export' to momanaqer, if you want try this in attachmentASRI éducation wrote:I just created a Puppy Precise version based on the latest version of woof-ce-testing (20150611).
My problem: I can not translate the last Zigbert interfaces.
momanager does not show me the files to translate.
An example: how do you translate pdesktop Apps?
Thank you in advance for your advice.
note: what other apps are not read by momanager?
- Attachments
-
- pdesktop_mod.tar.gz
- (1.04 KiB) Downloaded 671 times
[url]http://www.xanad.tk[/url] Html5 Parallax
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
MoManager
Code: Select all
#151001 translate also .md files (see function get_prop), use AUTHORSPECS in write.log, some code clean up
#151010 fixed pot for mdview; added path of zigbert's stardustlib
documentation files in .md format can be translated by momanager now. All about jamesbond's mdview
POT files for TEXTDOMAINS from .md files are showing full path script and line number as usual now.
zigbert's libstartdust located under /usr/lib had never be found by momanager before.
Now it is simply managed by having added path of libstardust in momanager's find GETTEXTSCRIPTS.
Download as usual from first page.
Re: MoManager
Thanks. Can you please show me an example of how a shell script would invoke mdview to show multi-language documentation?L18L wrote: documentation files in .md format can be translated by momanager now.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: MoManager - mdview support
There is nothing special to invoke from a shell script.step wrote:Thanks. Can you please show me an example of how a shell script would invoke mdview to show multi-language documentation?L18L wrote: documentation files in .md format can be translated by momanager now.
But let me make it clear by comparing with shell script.
In shell script it is:
Code: Select all
export TEXTDOMAIN=atextdomain
Code: Select all
%%textdomain anothertextdomain
mdview is looking for translations for each line (except those started with tab).
That's it.
Example: see http://www.murga-linux.com/puppy/viewto ... 714#865714
---
mdview is jamesbond's mdview available for fatdog in fatdog's package manager gslapt, maybe also in woof-CE soon.
I finally get it! The shell isn't involved in handling localized md documents; mdview does everything by itself. I like it. So a shell script can use mdview to show localized help files by simply including the classic stanza
for "help.md" like
Did I get it right?
Actually, I'm still confused. Suppose that a shell script has its own localized messages and displays a localized md file. How should TEXTDOMAIN and %%textdomain be specified? As the same name? If so, there would be a single .po file that mixes the shell catalog with the md catalog? How would I build the source pot file in this case?
Code: Select all
# set up localization
TEXTDOMAIN=name_of_shell_script_text_domain
export TEXTDOMAIN
# show help document
mdview "help.md"
Code: Select all
%%nopot yes
%%textdomain name_of_shell_script_text_domain
%%nopot no
# SHELL SCRIPT HELP FILE
Bla bla,
Actually, I'm still confused. Suppose that a shell script has its own localized messages and displays a localized md file. How should TEXTDOMAIN and %%textdomain be specified? As the same name? If so, there would be a single .po file that mixes the shell catalog with the md catalog? How would I build the source pot file in this case?
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
mdview
Maybe a bit "too" right.step wrote:I finally get it! The shell isn't involved in handling localized md documents; mdview does everything by itself. I like it. So a shell script can use mdview to show localized help files by simply including the classic stanzafor "help.md" likeCode: Select all
# set up localization TEXTDOMAIN=name_of_shell_script_text_domain export TEXTDOMAIN # show help document mdview "help.md"
Did I get it right?Code: Select all
%%nopot yes %%textdomain name_of_shell_script_text_domain %%nopot no # SHELL SCRIPT HELP FILE Bla bla,
You have declared and exported a TEXTDOMAIN in the shell script.
Thus your help.md can be just:
Code: Select all
# HELP
Bla bla,
Yes, do it manually:step wrote:Actually, I'm still confused. Suppose that a shell script has its own localized messages and displays a localized md file. How should TEXTDOMAIN and %%textdomain be specified? As the same name? If so, there would be a single .po file that mixes the shell catalog with the md catalog? How would I build the source pot file in this case?
append output of mdview --po ... to existing pot file.
If this is for your findnrun, try it this way and there is hope for momanager will use your "hand made" pot file.
@L18L
I just hacking your momanager a bit but then I thought I might not need to rediscover the wheel and ask.
The idea is to have momanager scan rootfs-skeleton and rootfs-packages in woof-CE and generate the pot files that can be then used for translations, each language in its own git folder.
For general use momanager could be modified to accept user-defined input and output directories if it does not already (does it ?).
This should not be too hard (from my little hacking).
What would be tricky I think, would be to go through existing pot and po files and change only what is new. And I guess for the pot files it could even rewrite them but you sure need to keep existing translation strings in the po files that are unaffected from the changes in the original scripts.
I know there are more complicated and efficient approaches for collaborative translations (pootle comes to mind) but I have the feeling that most translations are a single (or 2) person show.
Any thoughts?
I just hacking your momanager a bit but then I thought I might not need to rediscover the wheel and ask.
The idea is to have momanager scan rootfs-skeleton and rootfs-packages in woof-CE and generate the pot files that can be then used for translations, each language in its own git folder.
For general use momanager could be modified to accept user-defined input and output directories if it does not already (does it ?).
This should not be too hard (from my little hacking).
What would be tricky I think, would be to go through existing pot and po files and change only what is new. And I guess for the pot files it could even rewrite them but you sure need to keep existing translation strings in the po files that are unaffected from the changes in the original scripts.
I know there are more complicated and efficient approaches for collaborative translations (pootle comes to mind) but I have the feeling that most translations are a single (or 2) person show.
Any thoughts?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
hacking momanager
One note firstly, it is and I hope it will always be Barry's momanager.
I mean the idea and practice of this "all-in-ine" script for translating an entire distribution.
My additions came from practical translating, e.g. sorting,tunig for speed, caching, using fuzzy,etc
ASRI gave some input too
Barry again, (see comments in the script) could upgrade some messages about quirky and woof-Q
Thus any useful input of mavrothal would be appreciated.
Momanager was meant to be for translators only.
Developers when testing their work in progress, not being able to use the command line tools, should manually delete the actual pot file in /tmp/momanager if there have been changes concerning gettext then mightbe they could momanager too.
BTW, there are many messages that contain "Puppy" or "Quirky".
Using a variable for this would be very nice.("Puppy Slacko", "Puppy Tahr", ...) . Building a langpack would be changed.
Input is hardcoded at the moment, see "#find all gettext'ed scripts...", you are right: not too hard to change.
puppy localization [solved]
woof-(2|CE|Q) localization to be solved
I mean the idea and practice of this "all-in-ine" script for translating an entire distribution.
My additions came from practical translating, e.g. sorting,tunig for speed, caching, using fuzzy,etc
ASRI gave some input too
Barry again, (see comments in the script) could upgrade some messages about quirky and woof-Q
Thus any useful input of mavrothal would be appreciated.
Momanager was meant to be for translators only.
Developers when testing their work in progress, not being able to use the command line tools, should manually delete the actual pot file in /tmp/momanager if there have been changes concerning gettext then mightbe they could momanager too.
Sounds good. Would woof-Q be allowed to use them too?mavrothal wrote:The idea is to have momanager scan rootfs-skeleton and rootfs-packages in woof-CE and generate the pot files that can be then used for translations, each language in its own git folder.
BTW, there are many messages that contain "Puppy" or "Quirky".
Using a variable for this would be very nice.("Puppy Slacko", "Puppy Tahr", ...) . Building a langpack would be changed.
There is a /root/.config/momanager.conf, defining output directory o f language, e.g. pt or pt_BRmavrothal wrote:For general use momanager could be modified to accept user-defined input and output directories if it does not already (does it ?).
This should not be too hard (from my little hacking).
Input is hardcoded at the moment, see "#find all gettext'ed scripts...", you are right: not too hard to change.
No need for tricks and guesses. msgmerge is our friend.mavrothal wrote:What would be tricky I think, would be to go through existing pot and po files and change only what is new. And I guess for the pot files it could even rewrite them but you sure need to keep existing translation strings in the po files that are unaffected from the changes in the original scripts.
... the big advantage of our momanager IMHO: it is included and can be used immediately by anybody. Sharing their works is not everyone's hobby though. .mavrothal wrote:I know there are more complicated and efficient approaches for collaborative translations (pootle comes to mind) but I have the feeling that most translations are a single (or 2) person show.
puppy localization [solved]
woof-(2|CE|Q) localization to be solved
Re: hacking momanager
Not sure what " Would woof-Q be allowed to use them" means. Rootfs-skeleton in woof-Q and woof-CE share a lot of scripts and a lot of the common noarach pets are, well, common But I'm not sure will be drop in translation.L18L wrote:Sounds good. Would woof-Q be allowed to use them too?mavrothal wrote:The idea is to have momanager scan rootfs-skeleton and rootfs-packages in woof-CE and generate the pot files that can be then used for translations, each language in its own git folder.
BTW, there are many messages that contain "Puppy" or "Quirky".
Using a variable for this would be very nice.("Puppy Slacko", "Puppy Tahr", ...) . Building a langpack would be changed.
Regarding puppy version, putting in /etc/profile something like
Code: Select all
. /etc/DISTRO_SPECS
export Puppy="Puppy $DISTRO_FILE_PREFIX"
I had the feeling that momanager besides the output directory also puts mo files in /usr/share/locale. Doesn't it?L18L wrote:There is a /root/.config/momanager.conf, defining output directory o f language, e.g. pt or pt_BRmavrothal wrote:For general use momanager could be modified to accept user-defined input and output directories if it does not already (does it ?).
This should not be too hard (from my little hacking).
Input is hardcoded at the moment, see "#find all gettext'ed scripts...", you are right: not too hard to change.
How can you possible "hide" a text file. The moment is out you share it with everyone. Unless you are referring to "sharing the glory"L18L wrote:the big advantage of our momanager IMHO: it is included and can be used immediately by anybody. Sharing their works is not everyone's hobby though. .
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: hacking momanager
No, not in /usr/share/localemavrothal wrote:I had the feeling that momanager besides the output directory also puts mo files in /usr/share/locale. Doesn't it?L18L wrote:There is a /root/.config/momanager.conf, defining output directory o f language, e.g. pt or pt_BRmavrothal wrote:For general use momanager could be modified to accept user-defined input and output directories if it does not already (does it ?).
This should not be too hard (from my little hacking).
Input is hardcoded at the moment, see "#find all gettext'ed scripts...", you are right: not too hard to change.
Only in /usr/share/locale<language code>/LC_MESSAGES.
I am referring to people who searched an found help at the forum but never returned any language pack.mavrothal wrote:How can you possible "hide" a text file. The moment is out you share it with everyone. Unless you are referring to "sharing the glory"L18L wrote:the big advantage of our momanager IMHO: it is included and can be used immediately by anybody. Sharing their works is not everyone's hobby though. .
Re: hacking momanager
Right. But you do not want that if you just woofing around.L18L wrote:No, not in /usr/share/locale
Only in /usr/share/locale<language code>/LC_MESSAGES.
Also requiring a non-English locale to be in use so will run needs a workaround if it is just to generate the POT files.
L18L wrote:I am referring to people who searched an found help at the forum but never returned any language pack.
Unless you have specific persons in mind that you would expect to act differently for some reason, I think that this is the norm in forums like this one. Translation or otherwise.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: hacking momanager
Cannot image me just woofing around, really.mavrothal wrote:Right. But you do not want that if you just woofing around.
Also requiring a non-English locale to be in use so will run needs a workaround if it is just to generate the POT files.
Generating a pot file has nothing to do with locales.
If you mean po file msginit is the tool for this and msginit --help helps you to make use of option --locale.
The context was not "forums like this one" butmavrothal wrote:L18L wrote:I am referring to people who searched an found help at the forum but never returned any language pack.
Unless you have specific persons in mind that you would expect to act differently for some reason, I think that this is the norm in forums like this one. Translation or otherwise.
you wrote:more complicated and efficient approaches for collaborative translations
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
translation with mdview
No.step wrote:Did I get it right?
Here is how .md files can be translated.
Example: /usr/share/doc/findnrun/
Prepend
Code: Select all
%%textdomain docfindnrun
Code: Select all
momanager
Edit some messages.
Click OK (or Fix if you made some mistakes)
Click OK
Admire your translations (see image, made just some for demo)
Continue (last edited always at top of left-sire-top-combo box)
Click ........
Forget
Note, translators translate.[A] Instructions for markdown
The set of English markdown source files is located on github here.
Translate all .md files found in the on-line folder.
Pack all translated files into a .tar.gz archive named after your locale code, i.e. markdown[de_DE.UTF-8].tar.gz for German in Germany.
Send me the archive via one of the mechanisms noted above.
I will generate an HTML archive and push it to Github with the expectation that you will test the HTML archive and correct translation and layout issues by submitting new .md files until all issues are closed.
Note on markdown syntax
Avoid being too creative with your markdown syntax. Keep it simple. While the publishing process supports Markdown Extra I recommend that you stick to the much more limited, but effective, markdown syntax that mdview supports. All .md files in this project follow this guideline.
- Attachments
-
- docfindnrun_momanaged.png
- glued with PeasyGlue
- (157.56 KiB) Downloaded 469 times
Last edited by L18L on Tue 20 Oct 2015, 15:55, edited 1 time in total.
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
mdview
That's bad news.Known issues and limitations
Prioritized language preferences via environment variable LANGUAGE are not supported. Find-n-run honors the system locale code that environment variable LANG displays - when a matching translation file is installed.
In my system (all languages loades) this for example works:
Code: Select all
LANGUAGE=es findnrun
Code: Select all
LANGUAGE=zh_CN findnrun
- ASRI éducation
- Posts: 3197
- Joined: Sat 09 May 2009, 12:10
- Location: France
- Contact:
Re: MoManager
We could add a version date (always useful).L18L wrote:#151010
Regards
EDIT: this variable already exists. See below the message of L18L.
- Attachments
-
- momanager_20151021.jpg
- (72.68 KiB) Downloaded 1080 times
Last edited by ASRI éducation on Fri 23 Oct 2015, 09:27, edited 1 time in total.
Projet ASRI éducation => [url=http://asri-education.org/]Association[/url] | [url=http://forum.asri-education.org/]Forum[/url] | [url=http://dl01.asri-education.org/]Dépôt[/url] | [url=http://kids.asri-education.org/]Espace kids[/url]
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: MoManager
Yes, always useful.ASRI éducation wrote:We could add a version date (always useful).L18L wrote:#151010
Regards
At the moment the version is a tooltip for the "yellow star" icon at the bottom of main window.
It is somewhat hidden or should I say "not obvious"?
Putting it into the title bar is good.
But please: no new variable "AppVersion".
My "lastUPDATEofTHISscript" is automatically filled with the date of last comment, e.g. "#151021"
If this is in the title bar you can remove it from line 1872# grep -n lastUPDATEofTHISscript momanager
139:lastUPDATEofTHISscript="` grep -E '^$' -B 1 $0 | head -n 1 | cut -d ' ' -f1`" # sort of version
1872: <button tooltip-markup="<span>About momanager (date of last local database update is <b>${lastUPDATEofTHISscript}).</b></span>">
#
Cordialementjust to please our friend who wrote:_________________
"Logical entities must not be multiplied needlessly." / "Il ne faut pas multiplier les êtres logiques inutilement." (Ockham)
- ASRI éducation
- Posts: 3197
- Joined: Sat 09 May 2009, 12:10
- Location: France
- Contact:
Re: MoManager
Ok.L18L wrote:At the moment the version is a tooltip for the "yellow star" icon at the bottom of main window.
It is somewhat hidden or should I say "not obvious"?
Putting it into the title bar is good.
You've obviously right.L18L wrote:But please: no new variable "AppVersion".
My "lastUPDATEofTHISscript" is automatically filled with the date of last comment, e.g. "#151021"
Sorry, I had not noticed the variable lastUPDATEofTHISscript.
This variable indicates the modification date of the main script. In my humble opinion, this has no relation to the date of the database.L18L wrote:date of last local database update is $lastUPDATEofTHISscript
Some possible changes:
Code: Select all
--- ./momanager 2015-10-10 20:15:21.000000000 +0200
+++ /usr/sbin/momanager 2015-10-22 21:18:44.000000000 +0200
@@ -108,6 +108,7 @@
#150829 create_a_txz (fatdog package)
#151001 translate also .md files (see function get_prop), use AUTHORSPECS in write.log, some code clean up
#151010 fixed pot for mdview; added path of zigbert's stardustlib
+#151022 ASRI: add version information in title bar of main GUI
#***MOMANAGER IS ENGLISH ONLY (NOT GETTEXT'ED)***
#it is for use by developers/translators with knowledge of english.
@@ -133,7 +134,7 @@
[ "$2" ] && searchENTRY="$2" || searchENTRY='search term' #130604
-lastUPDATEofTHISscript="` grep -E '^$' -B 1 $0 | head -n 1 | cut -d ' ' -f1`" # sort of version
+lastUPDATEofTHISscript="` grep -E '^$' -B 1 $0 | head -n 1 | cut -d ' ' -f1 | cut -d '#' -f2`" # sort of version
# working directories
WD=/tmp/momanager; mkdir -p $WD #140308
@@ -255,7 +256,7 @@
ttSEARCH="${ttSEARCH} line of found '${searchENTRY}'"
[ "$CONTEXT_AFTER" -eq 1 ] && ttSEARCH="$ttSEARCH and $CONTEXT_AFTER line after"
[ "$CONTEXT_AFTER" -gt 1 ] && ttSEARCH="$ttSEARCH and $CONTEXT_AFTER lines after"
-ttSEARCH="${ttSEARCH}. (You can configure the number of these context lines in Preferences)"
+ttSEARCH="${ttSEARCH}. You can configure the number of these context lines in Preferences."
export LANG=C
. /etc/rc.d/PUPSTATE
@@ -1722,7 +1723,7 @@
if [ "$POEDITOR" ];then
[ -e /var/local/poedit_check ] && POEDIT_CHECK='true'
# POEDIT_XML="<checkbox><label>Tick to use poedit (instead of text editor)</label><default>${POEDIT_CHECK}</default><variable>POCHECK</variable></checkbox> <text><label>" "</label></text>"
- POEDIT_XML="<checkbox tooltip-markup="<span>Tick to use <b>poeditor</b> or untick to use <b>defaulttexteditor</b></span>"><label>Use poedit</label><default>${POEDIT_CHECK}</default><variable>POCHECK</variable></checkbox>"
+ POEDIT_XML="<checkbox tooltip-markup="<span>Tick to use <b>poeditor</b> or untick to use <b>defaulttexteditor</b>.</span>"><label>Use poedit</label><default>${POEDIT_CHECK}</default><variable>POCHECK</variable></checkbox>"
fi
#POEDIT_XML="$POEDIT_XML <text width-request="$(($WINDOW_WIDTH - 726 + 42))"><label>" "</label></text>" #130613 filler to keep buttons xalign left
@@ -1744,12 +1745,12 @@
#### main window
-MM2_DLG="<window title="MoManager : ${PUPPY} files" resizable="false" icon-name="${WINICON}">
+MM2_DLG="<window title="MoManager (v$lastUPDATEofTHISscript)" resizable="false" icon-name="${WINICON}">
<vbox>
<hbox>
- <text use-markup="true" width-request="$((WINDOW_WIDTH + 130))"><label>"First: you need to get all of the files on the right-side drop-down lists over to the left-side lists to ${TRANSLATE} to your <b>${transLANG}</b> language. Then check the left column to update/verify translations."</label></text>
+ <text use-markup="true" width-request="$((WINDOW_WIDTH + 130))"><label>"First, get all of the files on the right-side drop-down lists over to the left-side lists to ${TRANSLATE} to your <b>${transLANG}</b> language. Then, check the left column to update/verify translations."</label></text>
</hbox>
<hbox>
@@ -1855,7 +1856,7 @@
${POEDIT_XML}
<hbox>
- <entry width-chars="12" tooltip-markup="<span>Note, this search is <b>case sensitive</b>. To find all <i>please</i> or <i>Please</i> type: '<i>please|Please</i>' or just '<i>[p|P]lease</i>' (without the quotes!)</span>">
+ <entry width-chars="12" tooltip-markup="<span>Note, this search is <b>case sensitive</b>. To find all <i>please</i> or <i>Please</i> type: '<i>please|Please</i>' or just '<i>[p|P]lease</i>' (without the quotes!).</span>">
<default>$searchENTRY</default>
<variable>searchENTRY</variable>
</entry>
@@ -1866,10 +1867,11 @@
${PETHELP_XML}
- <button tooltip-markup="<span>About momanager (date of last local database update is <b>${lastUPDATEofTHISscript}).</b></span>">
+ <button tooltip-markup="<span>About momanager.</span>">
<input file stock="gtk-about"></input>
- <action>pupdialog --background '#8080FF' --backtitle 'MoManager: About' --msgbox 'Created by Barry Kauler for Puppy Linux. (c) Copyright Barry Kauler 2012, license GPL3 (refer /usr/share/doc/legal) \\n\\n \
- Forked by L18L 2013 for faster usage and for Fatdog ' 0 0 & </action></button>
+ <action>pupdialog --background '#8080FF' --backtitle 'MoManager: About' --msgbox 'Created by Barry Kauler for Puppy Linux. (c) Copyright Barry Kauler 2012, license GPL3 (refer /usr/share/doc/legal). \\n\\n \
+ Forked by L18L 2013 for faster usage and for Fatdog. \\n\\n \
+ Current version of momanager = $lastUPDATEofTHISscript. ' 0 0 & </action></button>
<button tooltip-text="Preferences: change some defaults in a text editor.">
<input file stock="gtk-preferences"></input>
@@ -1879,7 +1881,7 @@
<input file stock="gtk-refresh"></input>
<action>EXIT:refresh</action></button>
- <button tooltip-text="Create a ${LANGPACK}_${transLANG}.">
+ <button tooltip-markup="<span>Create a <b>${LANGPACK}_${transLANG}</b>.</span>">
<input file stock="gtk-yes"></input>
<action>EXIT:create_pet</action></button>
Très cordialement,
- Attachments
-
- momanager-20151022.tar.gz
- file /usr/sbin/momanager
- (34.86 KiB) Downloaded 584 times
Projet ASRI éducation => [url=http://asri-education.org/]Association[/url] | [url=http://forum.asri-education.org/]Forum[/url] | [url=http://dl01.asri-education.org/]Dépôt[/url] | [url=http://kids.asri-education.org/]Espace kids[/url]
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: MoManager
ASRI éducation wrote:This variable indicates the modification date of the main script. In my humble opinion, this has no relation to the date of the database.L18L wrote:date of last local database update is $lastUPDATEofTHISscript
Yes, and I even don‘t know what this „database" should be.
I cannot recall who has introduced „last local database update“.
Suggest to use just your „AppVersion“ for this and forget my „lastUPDATEofTHISscript“.
ASRI, I am glad to see your list of possible changes.
See my comments and make the changes please.
And I will point to this (your) AppVersion of momanger at page 1 of this thread.
Très très cordialement
My comments (hope that anyone understands them):
---
+#151022 ASRI: add version information in title bar of main GUI
OK
---
-lastUPDATEofTHISscript="‘ grep -E ‚^$‘ -B 1 $0 | head -n 1 | cut -d ' ' -f1‚“ # sort of version
+lastUPDATEofTHISscript="‘ grep -E ‚^$‘ -B 1 $0 | head -n 1 | cut -d ' ' -f1 | cut -d ‚#‘ -f2‚“ # sort of version
Insert 20 and everyone will see it is year
+AppVersion="20‘ grep -E ‚^$‘ -B 1 $0 | head -n 1 | cut -d
' ' -f1 | cut -d ‚#‘ -f2‚“
---
[ „$CONTEXT_AFTER“ -gt 1 ] && ttSEARCH="$ttSEARCH and $CONTEXT_AFTER lines after“
OK. (I have never used a change)
---
POEDIT
OK, the dot, point, full stop.
---
MM2_DLG
use AppVersion
---
remove text
“: you need to