tuxpaint-i18n — Discussion on internationalization and translation of Tux Paint

[Tuxpaint-i18n] New Magic tools added, need translating

[Bill K. <nb...@so...>]

Today I added two new Magic tools, and updated the strings to another.
So "tuxpaint" project's POT file has been updated, and PO files
sync'd with it over in the Git repository (and mirrored on my FTP).

Also, as a reminder, Tux Paint Config. has been reworked a bit,
so some strings changed over in that program's repo ("tuxpaint-config")
as well.

And finally, I've continued to update and tweak the documentation,
which was recently gettext-ified (and the Unix manpage is now, too!),
and lives in its own separate repo ("tuxpaint-docs").

(Miguel and Jacques, your Galician and French translations have both
dropped down to 79% complete since your latest contributions.)

So for those of you who have the time and inclination, please grab
the latest update to your locale's PO file from the Git repo or
via this page over on the Tux Paint website:  http://tuxpaint.org/help/po/

Thanks as always!

-- 
-bill!
Sent from my computer

[Tuxpaint-i18n] Making it possible to translate Tux Paint's Un*x manpage (tuxpaint.1)

[Bill K. <nb...@so...>]

My work to retool Tux Paint Config. to play more nicely
with larger screens, and better support localization,
had me realize that the organization of the options
inside Tux Paint Config. was pretty sensible.

I decided to reorganize the OPTIONS documentation (HTML/TXT)
to match it better, and then decided to take on the big task
of doing the same to Tux Paint's Unix manual page (manpage).

Then I got thinking, manpages get translated, too!  (In fact,
we had a Polish version... from 18 years ago!)  So I decided
to set up the manpage to be managed in the same way as the
HTML/TXT documentation.

"Source" for the man page (a plain text troff file) is
being injected with a bunch of PHP "<? =gettext("...") ?>"
around the text that makes sense to localize.

Already, since some of these strings existed in the other
doc files, you can see some of them appearing.

Here's some output from "LANG=gl_ES.UTF-8 man tuxpaint":

                [--printdelay=SEGUNDOS]
                [--printcfg]
                [--altprintalways | --altprintnever]
                [--papersize TAMA�O_DO_PAPEL | --papersize help]
                [--printcommand ORDE]
                [--altprintcommand ORDE]

Neat!

Anyway, so expect to see more strings appearing in the
"tuxpaint-docs" repository's POT and PO files soon!

-- 
-bill!
Sent from my computer

[Tuxpaint-i18n] Tux Paint Config. overhaul

[Bill K. <nb...@so...>]

I overhauled Tux Paint Config., in an attempt to make the UI
more dynamic (giving the appropriate space for longer localized
strings) and allowing it to run in a larger window, with a larger
font.  It's FAR from perfect, but it's quite an improvement.

As part of this, I rearrange some code, cleaned up a few strings
(causing some 'fuzzy'-ness), and just now added a ton of commentary
next to various gettext()-wrapped strings, in an attempt to help give
some context for the less obvious ones.

So, if you're localizing Tux Paint Config., please "git pull" from
the SourceForge Git repo to get the latest.  If you're not working
off of the Git repo (you should! :) ), you may grab the files
from the SF project page or my FTP server, via the links over here:

  http://tuxpaint.org/help/po/#tpc

(And as usual, feel free to post them to this list, or send them
to me directly, and we can get them committed to the Git repo on
your behalf.)

I hope you find it useful, and thanks as always for everyone's
efforts!

-- 
-bill!
Sent from my computer

[Tuxpaint-i18n] "First class" documentation translations copied to website for 0.9.26

[Bill K. <nb...@so...>]

FYI, I've copied the recently-(re)-translated Tux Paint documentation
over to the website, and rigged things up such that the links to each
doc file will go to the translated version, if the user visiting the
site is viewing it in one of these localizations:

  English
  French
  Galician
  Japanese

These are what I'm calling "first-class" translations, meaning they are
based on the latest docs for 0.9.26, and translasted via gettext and PO files.
Some of the other translations banging around on the website are quite ancinet.
(The earlier French version, for example, was from 0.9.14 :) )

As others provide translations of the docs (at least the main README),
I'll link to them as well.

You can see them via these links:

 * http://www.tuxpaint.org/docs/?lang=en_US
 * http://www.tuxpaint.org/docs/?lang=fr_FR
 * http://www.tuxpaint.org/docs/?lang=gl_ES
 * http://www.tuxpaint.org/docs/?lang=ja_JP

(Reminder, when you go to links like that, tuxpaint.org will set a cookie
noting your language preference.  So go here when you're done looking,
to go back to "[Using] Browser's Settings":

  http://www.tuxpaint.org/docs/?lang=default

I hope it all looks good!  And I'm hopeful that as search engines start
crawling these docs, it might help others find Tux Paint, or at least quickly
find help using it.  (I think many people don't know, or remember, that all
the docs _come_ with Tux Paint. ;) )

-- 
-bill!
Sent from my computer

[Tuxpaint-i18n] Last call for commits to 0.9.26 & friends!

[Bill K. <nb...@so...>]

I'm taking tomorrow (Monday 2021-06-28) off from work to recover from
some dental work, and if I have time I'd like to roll a release for
Tux Paint 0.9.26 & friends, since I've not heard any complaints about
the rc1 release we posted.  (I've asked around Twitter and the
"tuxpaint-users" mailing list.)

The only significant wrinkle right now is the 64-bit port for Haiku
isn't working, but since it's a very minor platform, in terms of Tux
Paint users, Luc says to just go ahead and proceed with this release.

So... if you have any last minute bug reports, translation updates, or
anything else you'd like to see included in 0.9.26, please commit it
to the source repository, or email it to me ASAP!

Thanks,

-- 
-bill!
Sent from my computer

Re: [Tuxpaint-i18n] [Tuxpaint-maintainers] Gearing up for Tux Paint 0.9.26

[Jacques C. <jac...@or...>]

Le 16/06/2021 à 08:19, Bill Kendrick a écrit :
.......................
> 
> I'd like to work on it after this release, though, if you
> think people can survive with it as-is. :)

I am not Gloria Gaynor, but i will survive ! :)

Jacques

Re: [Tuxpaint-i18n] [Tuxpaint-maintainers] Gearing up for Tux Paint 0.9.26

[Bill K. <nb...@so...>]

Oof yes, this is something I need to do at some point...
make Tux Paint Config less hard-coded, interface-wise,
and to allow for resizing, or at least some more scrolling.

I'd like to work on it after this release, though, if you
think people can survive with it as-is. :)

(We could always release TPC separately from TP, no reason
they have to always go at the same time... it's just that
new TP's usually add some feature that has a config option,
so a new TPC is required to support it.)

-bill!

On Tue, Jun 15, 2021 at 03:17:34PM +0200, Jacques Chion wrote:
> Le 14/06/2021 à 08:26, Pere Pujal i Carabantes a écrit :
> 
> >
> >Just to notice:
> >I've rebuild the translations for tuxpaint-config last night and that added a new string,
> >so those of you who want to keep your translation to 100% please check it again :)
> >
> 
> 
> I have a small problem with tuxpaint-config :
> the messages in English or American are rather short, so there are
> no difficulty to put it in tabs or buttons. It is difficult to do
> the same in French which is a little bit longer :(
> The size of the window for tuxpaint-config is 800x450.
> I am able to increase this size with a modification of tuxpaint-config2.cxx.
> Is it possible to modify the sources of tuxpaint-config to have a
> larger windows, so the translation will be be more comfortable. The
> ideal should be that the user can modify himself the size of the
> window :)
> 
> Regards
> 
> Jacques
> 
> 
> _______________________________________________
> Tuxpaint-i18n mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n

-- 
-bill!
Sent from my computer

Re: [Tuxpaint-i18n] [Tuxpaint-maintainers] Gearing up for Tux Paint 0.9.26

[Jacques C. <jac...@or...>]

Le 14/06/2021 à 08:26, Pere Pujal i Carabantes a écrit :

> 
> Just to notice:
> I've rebuild the translations for tuxpaint-config last night and that added a new string,
> so those of you who want to keep your translation to 100% please check it again :)
> 


I have a small problem with tuxpaint-config :
the messages in English or American are rather short, so there are no 
difficulty to put it in tabs or buttons. It is difficult to do the same 
in French which is a little bit longer :(
The size of the window for tuxpaint-config is 800x450.
I am able to increase this size with a modification of tuxpaint-config2.cxx.
Is it possible to modify the sources of tuxpaint-config to have a larger 
windows, so the translation will be be more comfortable. The ideal 
should be that the user can modify himself the size of the window :)

Regards

Jacques

Re: [Tuxpaint-i18n] [Tuxpaint-maintainers] Gearing up for Tux Paint 0.9.26

[Pere P. i C. <per...@gm...>]

El ds. 12 de 06 de 2021 a les 21:04 -0700, en/na Bill Kendrick va escriure:
> The next release of Tux Paint (0.9.26) is going to have
> some fun new features, and so far as I can tell, things
> look pretty stable so far.
> 
> School is about to end for my kids in a few weeks, so I'm
> thinking it'd be a good time to get a new release rolled out.
> (It'll also give us a few months to track down any bugs that
> end users out in the real world find, before school starts back
> up in fall (well, here in the Northern Hemisphere at least).)
> 
> So...
> 
> Translators, if you have the time and energy, please get me your
> latest PO files so I can integrate them, and you can see the results
> in any release candidate versions we get built.

Just to notice:
I've rebuild the translations for tuxpaint-config last night and that added a new string, 
so those of you who want to keep your translation to 100% please check it again :)

Pere


> And maintainers, please check that Tux Paint is building and operating
> properly for you.  You can do it right now, by pulling the code from
> the various Git repositories.  In the next few days I'll roll together
> a source tarball for official release candidates as well, and perhaps
> we can have people beta test before a final release of 0.9.26.
> 
> Thanks & I hope everyone is staying well out there!
> 

Re: [Tuxpaint-i18n] Press releases to be gettext-based from now on

[Bill K. <nb...@so...>]

On Sat, Jun 12, 2021 at 07:00:10PM -0700, Bill Kendrick wrote:
> 
> And what I currently have for 0.9.26's press release has
> been wrapped in gettext() and the strings can be found in the
> "tuxpaint-website.pot" catalog.  (It adds 27 new strings,
> though some of them are paragraph length :) )

My wife (editor extraordinaire) helped me edit it a little today,
which I've just committed...


PS - Miguel noticed that the stats and PO downloads for the new
'tuxpaint-docs' were missing from the website.  Turns out my
shell script was silently failing to run some steps, because
apparently the "rename" file-renaming tool is now in its own
package, which I had to install.  (I recently updated the OS on the
server hosting tuxpaint.org.)  Fixed!

-bill!

[Tuxpaint-i18n] Gearing up for Tux Paint 0.9.26

[Bill K. <nb...@so...>]

The next release of Tux Paint (0.9.26) is going to have
some fun new features, and so far as I can tell, things
look pretty stable so far.

School is about to end for my kids in a few weeks, so I'm
thinking it'd be a good time to get a new release rolled out.
(It'll also give us a few months to track down any bugs that
end users out in the real world find, before school starts back
up in fall (well, here in the Northern Hemisphere at least).)

So...

Translators, if you have the time and energy, please get me your
latest PO files so I can integrate them, and you can see the results
in any release candidate versions we get built.

And maintainers, please check that Tux Paint is building and operating
properly for you.  You can do it right now, by pulling the code from
the various Git repositories.  In the next few days I'll roll together
a source tarball for official release candidates as well, and perhaps
we can have people beta test before a final release of 0.9.26.

Thanks & I hope everyone is staying well out there!

-- 
-bill!
Sent from my computer

Re: [Tuxpaint-i18n] Press releases to be gettext-based from now on

[Bill K. <nb...@so...>]

And what I currently have for 0.9.26's press release has
been wrapped in gettext() and the strings can be found in the
"tuxpaint-website.pot" catalog.  (It adds 27 new strings,
though some of them are paragraph length :) )

Let me know if you notice any issues or have any questions!

[*]
See stats and links to it and the PO files here:
http://tuxpaint.org/help/po/#tpw



On Sat, Jun 12, 2021 at 02:52:21PM -0700, Bill Kendrick wrote:
> 
> I've transformed the PHP file for what will be
> the press release for the next version (0.9.26) of
> Tux Paint into a 'standard' style page (with the sidebar
> of links down the side, yellow styling, etc.),
> so that -- once I wrap the strings in gettext() -- it
> will be a lot simpler to translate.  (No need for a separate
> PHP+HTML file for every translation, like we've done in the
> past.)
> 
> I also realized that the "Press Releases" page itself
> (http://www.tuxpaint.org/latest/) was not gettext'ized,
> so I've just done that.
> 
> Just a heads-up!
> 
> -- 
> -bill!
> Sent from my computer
> 
> 
> _______________________________________________
> Tuxpaint-i18n mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n

-- 
-bill!
Sent from my computer

[Tuxpaint-i18n] Press releases to be gettext-based from now on

[Bill K. <nb...@so...>]

I've transformed the PHP file for what will be
the press release for the next version (0.9.26) of
Tux Paint into a 'standard' style page (with the sidebar
of links down the side, yellow styling, etc.),
so that -- once I wrap the strings in gettext() -- it
will be a lot simpler to translate.  (No need for a separate
PHP+HTML file for every translation, like we've done in the
past.)

I also realized that the "Press Releases" page itself
(http://www.tuxpaint.org/latest/) was not gettext'ized,
so I've just done that.

Just a heads-up!

-- 
-bill!
Sent from my computer

Re: [Tuxpaint-i18n] Making a call for translators

[Jacques C. <jac...@or...>]

Le 01/05/2021 à 19:13, Bill Kendrick a écrit :

Hello Bill and everybody !
..............
> And as a reminder, the documentation for Tux Paint was recently
> convert to PHP scripts with all the text wrapped in gettext(),
> so translations of the doc files (README, OPTIONS, EXTENDING, etc.)
> should now be MUCH easier for you to maintain... it's just PO files,
> like the rest of the project.  (It'll look very similar to you
> if you've worked on translating the website.)

yes, but these documents represent 1118 items to translate :)

I started with the translation of the 'Advanced Stamps HOWTO' which is 
very technical, and i hope i did not too much mistakes. If somebody 
reading french and using image editors fluently, i will be happy to fix 
my errors.

And on anotjer hand, i had 2 errors with poedit with this document.
The first with the line beginning with 'Use the clone tool ...', and the 
second with the line beginning with 'It is very easy to ruin your hard 
work ...'.
These errors are similar :

   Error: 'msgstr' is not a valid PHP format string, unlike 'msgid'. 
Reason: In the directive number 2, the character ')' is not a valid 
conversation specifier.
  (for the first)
and

Error: 'msgstr' is not a valid PHP format string, unlike 'msgid'. 
Reason: In the directive number 2, the character 'n' is not a valid 
conversation specifier.

(For the second)

i don't see how to fix this error. Any idea ?
>
...................
> 
  I hope everyone is staying well!
I also

All the best

Jacques

[Tuxpaint-i18n] Making a call for translators

[Bill K. <nb...@so...>]

Today I've been going through a list of the most out-of-date Tux Paint
(main program) translations (e.g., Shuswap hasn't been updated since 2008),
and posting calls for help to Twitter.  When possible, I've used (abused?)
Google Translate to re-post the same request in each particular language.

In the meantime, if anyone out here feels like dusting off their PO files,
please do so and get them to me whenever you're ready.

Please don't feel like you need to get it to 100% before sending me
something... iterative updates are fine, and help ensure that your
hard work gets its chance to land in the next release, if you get too
busy to work on it for a while, and/or I 'jump' and cut a release.

And as a reminder, the documentation for Tux Paint was recently
convert to PHP scripts with all the text wrapped in gettext(),
so translations of the doc files (README, OPTIONS, EXTENDING, etc.)
should now be MUCH easier for you to maintain... it's just PO files,
like the rest of the project.  (It'll look very similar to you
if you've worked on translating the website.)

So far, I've only received French (a tiny bit), Japanese (about 50%),
and Galician (Miguel has been keeping it at 100% at all times!).

To learn more, visit http://www.tuxpaint.org/help/#translating
and if you're not using Git yet, you can download the PO files
from http://www.tuxpaint.org/help/po/

Thanks as always!  I hope everyone is staying well!

-- 
-bill!
Sent from my computer

Re: [Tuxpaint-i18n] Some comment regarding document "OPTIONS"

[Bill K. <nb...@so...>]

On Wed, Mar 24, 2021 at 05:34:23PM +0900, Shin-ichi TOYAMA wrote:
>    O.K.
>    Before doing it myself, I will be happy if someone let me know what the
>    modifire key on macOS is.
>    Mark?

For coarse keyboard movement, it should be [Shift] on all
platforms.  Per handle_keymouse():

      /* If Shift is pressed, go with the defaults */
      if (!(SDL_GetModState() & KMOD_SHIFT))

Unless I'm confused/mistaken. :)

-bill!

>    2021/03/24 15:56 Bill Kendrick <nb...@so...>:
> 
> 
>      This all sounds fine to me.  Would you be willing to
>      make the modifications to the 'source' (OPTIONS.php)?
>      Or would you like me to make an attempt?
> 
>      A little of what you say is unclear to me (partly
>      written-language-related, but mostly due to my inexperience
>      with Windows :-D )
> 
>      Let me know!  Thanks,
> 
>      -bill!
> 
>      On Thu, Mar 18, 2021 at 05:09:07PM +0900, TOYAMA Shin-ichi wrote:
>      > Hi!
>      >
>      > I finished translating "OPTIONS" and committed it.
>      >
>      > By the way, there are a few things I noticed while translating it
>      > that I would like to mention below.
>      >
>      > 1) modifier key for the coarse cursor movement while using
>      >     keyboard operation.
>      >
>      > There supposed to be no "default" key on standard keyboard for
>      > windows, and the "Shift" key works as a modifier key for the
>      > coarse cursor movement on my environment.
>      >
>      > How about describing as follows ?
>      > --
>      > Fine movement within canvas, or coarse movement if modifier
>      > key ("%1$s" on Unix/Linux, "%2$s" on Windows and "%3$s
>      > on macOS) is held.
>      > --
>      >
>      > 2) Export directory on Windows
>      >
>      >   I propose following description.
>      > --
>      > "My Pictures" directory for each user.<br>You can confirm
>      > actual location (normaly "c:\Users\<i>Username</i>\Pictures") by
>      > issuing command "echo %My Pictures%" on the command prompt.
>      > You can directly open the folder as follows;
>      >  * Press [Windows]+[R] to open �"Run ...�" dialogue.
>      >  * Enter "Shell:My Pictures" in the text box and push [OK].
>      > --
>      >  
>      > 3) The way to set environment variable on Windows.
>      >
>      > "autoexec.bat" and "sysedit" is quite obsolete (only available
>      > on before Windows Me).
>      >
>      > Access to the configuration dialogue using GUI is quite complicated
>      > and different version to version.
>      > I suppose the following way goes straightforward and not different
>      > among all versions.
>      >
>      >  * Press [Windows]+[R] to open "uRun ...�" dialogue.
>      >  * Enter "sysdm.cpl" in the text box and push [OK] button to open
>      >    "System properties" dialogue.
>      >  * Select "Advanced" tab.
>      >  * Click "Environment Variables..." button.
>      >  * Edit the value of the parameter "LANG" (should be newly created
>      >     if not exists).
>      >
>      > Thanks!
>      >
>      > --
>      > TOYAMA Shin-ichi mailto:sh...@wm...
>      >
>      >
>      > _______________________________________________
>      > Tuxpaint-i18n mailing list
>      > Tux...@li...
>      > https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
> 
>      --
>      -bill!
>      Sent from my computer
> 
> 
>      _______________________________________________
>      Tuxpaint-i18n mailing list
>      Tux...@li...
>      https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n


> _______________________________________________
> Tuxpaint-i18n mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n


-- 
-bill!
Sent from my computer

Re: [Tuxpaint-i18n] Some comment regarding document "OPTIONS"

[Shin-ichi T. <sh...@wm...>]

<div dir='auto'>O.K.<div dir="auto"><br><div dir="auto">Before doing it myself, I will be happy if someone let me know what the modifire key on macOS is.</div><div dir="auto"><br></div><div dir="auto">Mark?</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2021/03/24 15:56 Bill Kendrick &lt;nb...@so...&gt;:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">&#13;<br>
This all sounds fine to me.&nbsp; Would you be willing to&#13;<br>
make the modifications to the 'source' (OPTIONS.php)?&#13;<br>
Or would you like me to make an attempt?&#13;<br>
&#13;<br>
A little of what you say is unclear to me (partly&#13;<br>
written-language-related, but mostly due to my inexperience&#13;<br>
with Windows :-D )&#13;<br>
&#13;<br>
Let me know!&nbsp; Thanks,&#13;<br>
&#13;<br>
-bill!&#13;<br>
&#13;<br>
On Thu, Mar 18, 2021 at 05:09:07PM +0900, TOYAMA Shin-ichi wrote:&#13;<br>
&gt; Hi!&#13;<br>
&gt; &#13;<br>
&gt; I finished translating "OPTIONS" and committed it.&#13;<br>
&gt; &#13;<br>
&gt; By the way, there are a few things I noticed while translating it &#13;<br>
&gt; that I would like to mention below.&#13;<br>
&gt; &#13;<br>
&gt; 1) modifier key for the coarse cursor movement while using &#13;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; keyboard operation.&#13;<br>
&gt; &#13;<br>
&gt; There supposed to be no "default" key on standard keyboard for&#13;<br>
&gt; windows, and the "Shift" key works as a modifier key for the &#13;<br>
&gt; coarse cursor movement on my environment.&#13;<br>
&gt; &#13;<br>
&gt; How about describing as follows ?&#13;<br>
&gt; --&#13;<br>
&gt; Fine movement within canvas, or coarse movement if modifier&#13;<br>
&gt; key ("%1$s" on Unix/Linux, "%2$s" on Windows and "%3$s &#13;<br>
&gt; on macOS) is held.&#13;<br>
&gt; --&#13;<br>
&gt; &#13;<br>
&gt; 2) Export directory on Windows&#13;<br>
&gt; &#13;<br>
&gt;&nbsp;&nbsp; I propose following description.&#13;<br>
&gt; --&#13;<br>
&gt; "My Pictures" directory for each user.&lt;br&gt;You can confirm&#13;<br>
&gt; actual location (normaly "c:\Users\&lt;i&gt;Username&lt;/i&gt;\Pictures") by &#13;<br>
&gt; issuing command "echo %My Pictures%" on the command prompt.&#13;<br>
&gt; You can directly open the folder as follows;&#13;<br>
&gt;&nbsp; * Press [Windows]+[R] to open &#65533;"Run ...&#65533;" dialogue.&#13;<br>
&gt;&nbsp; * Enter "Shell:My Pictures" in the text box and push [OK].&#13;<br>
&gt; --&#13;<br>
&gt;&nbsp;&nbsp; &#13;<br>
&gt; 3) The way to set environment variable on Windows.&#13;<br>
&gt; &#13;<br>
&gt; "autoexec.bat" and "sysedit" is quite obsolete (only available &#13;<br>
&gt; on before Windows Me).&#13;<br>
&gt; &#13;<br>
&gt; Access to the configuration dialogue using GUI is quite complicated&#13;<br>
&gt; and different version to version.&#13;<br>
&gt; I suppose the following way goes straightforward and not different &#13;<br>
&gt; among all versions.&#13;<br>
&gt; &#13;<br>
&gt;&nbsp; * Press [Windows]+[R] to open "uRun ...&#65533;" dialogue.&#13;<br>
&gt;&nbsp; * Enter "sysdm.cpl" in the text box and push [OK] button to open&#13;<br>
&gt;&nbsp;&nbsp;&nbsp; "System properties" dialogue.&#13;<br>
&gt;&nbsp; * Select "Advanced" tab.&#13;<br>
&gt;&nbsp; * Click "Environment Variables..." button.&#13;<br>
&gt;&nbsp; * Edit the value of the parameter "LANG" (should be newly created&#13;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; if not exists).&#13;<br>
&gt; &#13;<br>
&gt; Thanks!&#13;<br>
&gt; &#13;<br>
&gt; -- &#13;<br>
&gt; TOYAMA Shin-ichi mailto:sh...@wm...&#13;<br>
&gt; &#13;<br>
&gt; &#13;<br>
&gt; _______________________________________________&#13;<br>
&gt; Tuxpaint-i18n mailing list&#13;<br>
&gt; Tux...@li...&#13;<br>
&gt; https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n&#13;<br>
&#13;<br>
-- &#13;<br>
-bill!&#13;<br>
Sent from my computer&#13;<br>
&#13;<br></p>
<p dir="ltr">_______________________________________________&#13;<br>
Tuxpaint-i18n mailing list&#13;<br>
Tux...@li...&#13;<br>
https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n&#13;<br>
</p>
</blockquote></div><br></div>

Re: [Tuxpaint-i18n] Some comment regarding document "OPTIONS"

[Bill K. <nb...@so...>]

This all sounds fine to me.  Would you be willing to
make the modifications to the 'source' (OPTIONS.php)?
Or would you like me to make an attempt?

A little of what you say is unclear to me (partly
written-language-related, but mostly due to my inexperience
with Windows :-D )

Let me know!  Thanks,

-bill!

On Thu, Mar 18, 2021 at 05:09:07PM +0900, TOYAMA Shin-ichi wrote:
> Hi!
> 
> I finished translating "OPTIONS" and committed it.
> 
> By the way, there are a few things I noticed while translating it 
> that I would like to mention below.
> 
> 1) modifier key for the coarse cursor movement while using 
>     keyboard operation.
> 
> There supposed to be no "default" key on standard keyboard for
> windows, and the "Shift" key works as a modifier key for the 
> coarse cursor movement on my environment.
> 
> How about describing as follows ?
> --
> Fine movement within canvas, or coarse movement if modifier
> key ("%1$s" on Unix/Linux, "%2$s" on Windows and "%3$s 
> on macOS) is held.
> --
> 
> 2) Export directory on Windows
> 
>   I propose following description.
> --
> "My Pictures" directory for each user.<br>You can confirm
> actual location (normaly "c:\Users\<i>Username</i>\Pictures") by 
> issuing command "echo %My Pictures%" on the command prompt.
> You can directly open the folder as follows;
>  * Press [Windows]+[R] to open "Run ..." dialogue.
>  * Enter "Shell:My Pictures" in the text box and push [OK].
> --
>   
> 3) The way to set environment variable on Windows.
> 
> "autoexec.bat" and "sysedit" is quite obsolete (only available 
> on before Windows Me).
> 
> Access to the configuration dialogue using GUI is quite complicated
> and different version to version.
> I suppose the following way goes straightforward and not different 
> among all versions.
> 
>  * Press [Windows]+[R] to open "uRun ..." dialogue.
>  * Enter "sysdm.cpl" in the text box and push [OK] button to open
>    "System properties" dialogue.
>  * Select "Advanced" tab.
>  * Click "Environment Variables..." button.
>  * Edit the value of the parameter "LANG" (should be newly created
>     if not exists).
> 
> Thanks!
> 
> -- 
> TOYAMA Shin-ichi mailto:sh...@wm...
> 
> 
> _______________________________________________
> Tuxpaint-i18n mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n

-- 
-bill!
Sent from my computer

[Tuxpaint-i18n] Some comment regarding document "OPTIONS"

[TOYAMA Shin-i. <sh...@wm...>]

Hi!

I finished translating "OPTIONS" and committed it.

By the way, there are a few things I noticed while translating it 
that I would like to mention below.

1) modifier key for the coarse cursor movement while using 
    keyboard operation.

There supposed to be no "default" key on standard keyboard for
windows, and the "Shift" key works as a modifier key for the 
coarse cursor movement on my environment.

How about describing as follows ?
--
Fine movement within canvas, or coarse movement if modifier
key ("%1$s" on Unix/Linux, "%2$s" on Windows and "%3$s 
on macOS) is held.
--

2) Export directory on Windows

  I propose following description.
--
"My Pictures" directory for each user.<br>You can confirm
actual location (normaly "c:\Users\<i>Username</i>\Pictures") by 
issuing command "echo %My Pictures%" on the command prompt.
You can directly open the folder as follows;
 * Press [Windows]+[R] to open "Run ..." dialogue.
 * Enter "Shell:My Pictures" in the text box and push [OK].
--
  
3) The way to set environment variable on Windows.

"autoexec.bat" and "sysedit" is quite obsolete (only available 
on before Windows Me).

Access to the configuration dialogue using GUI is quite complicated
and different version to version.
I suppose the following way goes straightforward and not different 
among all versions.

 * Press [Windows]+[R] to open "uRun ..." dialogue.
 * Enter "sysdm.cpl" in the text box and push [OK] button to open
   "System properties" dialogue.
 * Select "Advanced" tab.
 * Click "Environment Variables..." button.
 * Edit the value of the parameter "LANG" (should be newly created
    if not exists).

Thanks!

-- 
TOYAMA Shin-ichi mailto:sh...@wm...

Re: [Tuxpaint-i18n] [Tuxpaint-devel] Migrating Tux Paint's docs to its own repo for PO (gettext) translation

[TOYAMA Shin-i. <sh...@wm...>]

Hi,

Translating '%B %e, %Y' as '%Y<NEN>%B%e<NICHI>' resulted
'2021<NEN>3<GATSU> 9<NICHI>' which is almost the same with, 
and a little better than the output from 'strftime("%x", mktime(...; ' 
that is '2021<NEN>03<GATSU>09<NICHI>'.

*) <NEN>, <GATSU> and <NICHI> represents Kanji characters for
    Year, Month and Day respectively.

It is completely fine.
Thanks!

Bill Kendrick wrote in <202...@sh...>
>Okay I hate %x ("Preferred date representation based on locale") in English.
>("03/09/21" nonsense!!!)
>
>So I'm going to have the gettext()'d format string for strftime() be
>this, which everyone can simply replace in their localization
>(e.g., "%Y-%m-%d" or just "%F", if you want ISO 8601 "YYYY-MM-DD"
>format, which I do love for technical use.)
>
>  %B %e, %Y
>
>That's full month name (_should_ be localized), one digit day,
>four digit year.  So in English:
>
>  March 9, 2021
>
>
>I realize this is almost identical to what I had before ("%e %B %Y"),
>_but_, since the format string is now wrapped in gettext(), hopefully
>it will be more flexible. :)
>
>
>-bill!
>
>
>On Sun, Mar 07, 2021 at 01:01:31PM -0500, Mark Kim wrote:
>> > > Would it be easier to just do
>> > >
>> > >     <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>
>> > >
>> > > .. and skip month_names[], its lookup, relying on the user to figure out
>> > > how to "translate" "%1\$s %2\$s %3\$s", and documenting how to
>> translate it?
>> >
>> > Would this address Shin-Ichi's issue?
>
>
>_______________________________________________
>Tuxpaint-devel mailing list
>Tux...@li...
>https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel

-- 
TOYAMA Shin-ichi mailto:sh...@wm...

Re: [Tuxpaint-i18n] [Tuxpaint-devel] Migrating Tux Paint's docs to its own repo for PO (gettext) translation

[Miguel B. <mbo...@gm...>]

I search for "strftime" and I always find a lot of manual pages about it,
then it's a matter of having some logical thinking to know which is the
format of your language.
In my language it is: day of month of year
%e de %B de %Y

https://www.php.net/manual/en/function.strftime.php

O mér., 10 de mar. de 2021 ás 09:35, Sveinn í Felli (<sv...@fe...>)
escribiu:

> For translators it may be nice to be pointed towards some of the
> websites instructing how to build strftime-expressions, example:
> <https://www.foragoodstrftime.com/>.
>
> Quite often the translation-comment is something like:
> #. This is the time format used in the "Date Modified" column and
> #. * in the Properties dialog.  See the man page of strftime for an
> #. * explanation of the values.
>
> Such a comment is limited to Linux and perhaps a handful of applications
> on other platforms, unless linked to any of the web-based versions of
> strftime man pages; e.g.:
> <https://man7.org/linux/man-pages/man3/strftime.3.html>
>
> In the Ubuntu indicator-datetime.po is this comment:
> #. TRANSLATORS: A format string for the strftime function for
> #. a clock showing the day of the week and the time in 24-hour format
> without
> #. seconds.  Information is available in this Launchpad answer:
> #.
>
> https://answers.launchpad.net/ubuntu/+source/indicator-datetime/+question/149752
>
> Which is awful because it does not give any hint on how to build
> strftime-expressions, but then, there's a link to a manpage.
>
> I'd prefer the friendly interface of <https://www.foragoodstrftime.com/>
> or other similar website (there's a handful of them).
>
> Just thoughts,
> Sveinn í Felli
>
> P.S.: In my dearest Icelandic, the 'natural' expression is "%e. %B %Y -
> %H:%M:%S" and the 'scientific' one is "%F".
>
>
> Þann 10.3.2021 05:22, skrifaði Bill Kendrick:
> >
> > Okay I hate %x ("Preferred date representation based on locale") in
> English.
> > ("03/09/21" nonsense!!!)
> >
> > So I'm going to have the gettext()'d format string for strftime() be
> > this, which everyone can simply replace in their localization
> > (e.g., "%Y-%m-%d" or just "%F", if you want ISO 8601 "YYYY-MM-DD"
> > format, which I do love for technical use.)
> >
> >    %B %e, %Y
> >
> > That's full month name (_should_ be localized), one digit day,
> > four digit year.  So in English:
> >
> >    March 9, 2021
> >
> >
> > I realize this is almost identical to what I had before ("%e %B %Y"),
> > _but_, since the format string is now wrapped in gettext(), hopefully
> > it will be more flexible. :)
> >
> >
> > -bill!
> >
> >
> > On Sun, Mar 07, 2021 at 01:01:31PM -0500, Mark Kim wrote:
> >>>> Would it be easier to just do
> >>>>
> >>>>      <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>
> >>>>
> >>>> .. and skip month_names[], its lookup, relying on the user to figure
> out
> >>>> how to "translate" "%1\$s %2\$s %3\$s", and documenting how to
> >> translate it?
> >>>
> >>> Would this address Shin-Ichi's issue?
> >
> >
> > _______________________________________________
> > Tuxpaint-i18n mailing list
> > Tux...@li...
> > https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
> >
>
>
>
> _______________________________________________
> Tuxpaint-i18n mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
>


-- 
Membro do «Grupo de Amigos GNU/Linux de Pontevedra (GALPon)»
http://galpon.org
Membro de «Proxecto Trasno» http://trasno.gal
Co-coordinador do proxecto «GALPon MiniNo» http://minino.galpon.org

Re: [Tuxpaint-i18n] [Tuxpaint-devel] Migrating Tux Paint's docs to its own repo for PO (gettext) translation

[Sveinn í F. <sv...@fe...>]

For translators it may be nice to be pointed towards some of the 
websites instructing how to build strftime-expressions, example:
<https://www.foragoodstrftime.com/>.

Quite often the translation-comment is something like:
#. This is the time format used in the "Date Modified" column and
#. * in the Properties dialog.  See the man page of strftime for an
#. * explanation of the values.

Such a comment is limited to Linux and perhaps a handful of applications 
on other platforms, unless linked to any of the web-based versions of 
strftime man pages; e.g.: 
<https://man7.org/linux/man-pages/man3/strftime.3.html>

In the Ubuntu indicator-datetime.po is this comment:
#. TRANSLATORS: A format string for the strftime function for
#. a clock showing the day of the week and the time in 24-hour format 
without
#. seconds.  Information is available in this Launchpad answer:
#. 
https://answers.launchpad.net/ubuntu/+source/indicator-datetime/+question/149752

Which is awful because it does not give any hint on how to build 
strftime-expressions, but then, there's a link to a manpage.

I'd prefer the friendly interface of <https://www.foragoodstrftime.com/> 
or other similar website (there's a handful of them).

Just thoughts,
Sveinn í Felli

P.S.: In my dearest Icelandic, the 'natural' expression is "%e. %B %Y - 
%H:%M:%S" and the 'scientific' one is "%F".


Þann 10.3.2021 05:22, skrifaði Bill Kendrick:
> 
> Okay I hate %x ("Preferred date representation based on locale") in English.
> ("03/09/21" nonsense!!!)
> 
> So I'm going to have the gettext()'d format string for strftime() be
> this, which everyone can simply replace in their localization
> (e.g., "%Y-%m-%d" or just "%F", if you want ISO 8601 "YYYY-MM-DD"
> format, which I do love for technical use.)
> 
>    %B %e, %Y
> 
> That's full month name (_should_ be localized), one digit day,
> four digit year.  So in English:
> 
>    March 9, 2021
> 
> 
> I realize this is almost identical to what I had before ("%e %B %Y"),
> _but_, since the format string is now wrapped in gettext(), hopefully
> it will be more flexible. :)
> 
> 
> -bill!
> 
> 
> On Sun, Mar 07, 2021 at 01:01:31PM -0500, Mark Kim wrote:
>>>> Would it be easier to just do
>>>>
>>>>      <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>
>>>>
>>>> .. and skip month_names[], its lookup, relying on the user to figure out
>>>> how to "translate" "%1\$s %2\$s %3\$s", and documenting how to
>> translate it?
>>>
>>> Would this address Shin-Ichi's issue?
> 
> 
> _______________________________________________
> Tuxpaint-i18n mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
> 

Re: [Tuxpaint-i18n] [Tuxpaint-devel] Migrating Tux Paint's docs to its own repo for PO (gettext) translation

[Bill K. <nb...@so...>]

Okay I hate %x ("Preferred date representation based on locale") in English.
("03/09/21" nonsense!!!)

So I'm going to have the gettext()'d format string for strftime() be
this, which everyone can simply replace in their localization
(e.g., "%Y-%m-%d" or just "%F", if you want ISO 8601 "YYYY-MM-DD"
format, which I do love for technical use.)

  %B %e, %Y

That's full month name (_should_ be localized), one digit day,
four digit year.  So in English:

  March 9, 2021


I realize this is almost identical to what I had before ("%e %B %Y"),
_but_, since the format string is now wrapped in gettext(), hopefully
it will be more flexible. :)


-bill!


On Sun, Mar 07, 2021 at 01:01:31PM -0500, Mark Kim wrote:
> > > Would it be easier to just do
> > >
> > >     <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>
> > >
> > > .. and skip month_names[], its lookup, relying on the user to figure out
> > > how to "translate" "%1\$s %2\$s %3\$s", and documenting how to
> translate it?
> >
> > Would this address Shin-Ichi's issue?

Re: [Tuxpaint-i18n] [Tuxpaint-devel] Migrating Tux Paint's docs to its own repo for PO (gettext) translation

[TOYAMA Shin-i. <sh...@wm...>]

Hi,

Mark Kim wrote in <CAD...@ma...>
>> >     <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>

I tested it and the results looks quite fine.

Mark's other recomendations and Karl's proposal to use ISO-8601 
are also reasonable for me.

Thanks.

>> > .. and skip month_names[], its lookup, relying on the user to figure out
>> > how to "translate" "%1\$s %2\$s %3\$s", and documenting how to
>translate it?
>>
>> Would this address Shin-Ichi's issue?
>
>It does, and the output does come out "correct" for all languages libc has
>locale data for, but the European language output uses numerals instead of
>the full month names which feels less polished.  So for US English it
>outputs "01/30/2021" instead of "January 30, 2021", for French it outputs
>"30/01/2021" instead of "30 janvier 2021", etc. C is the worst, outputting
>"01/30/21" instead of something more sensible like "2021-01-30" (ISO
>standard).
>
>If we want the output to be correct for all languages by default but be
>able to polish it up for some select languages something like this may be
>reasonable:
>
><?= strftime(gettext("%x"), strtotime("2021-01-30")) ?>
>
>
>... and let each language override "%x" (localized default) with "%e %B %Y"
>("30 January 2021") or "%B %e, %Y" ("January 30, 2021) or "%F"
>("2021-01-30").
>
>If having gettext("%x") everywhere is a problem it can be wrapped with a
>function like so once in include.php:
>
>function localized_date($date) {
>  return strftime(gettext("%x"), strtotime($date));
>}
>
>
>... then called like so from other php files:
>
><?= localized_date("2021-01-30") ?>
>
>
>Mark
>
>On Sun, Mar 7, 2021 at 1:25 AM Bill Kendrick <nb...@so...> wrote:
>
>> On Fri, Mar 05, 2021 at 11:19:26PM -0500, Mark Kim wrote:
>> > > <?= sprintf(gettext("%1\$s %2\$s %3\$s"), 5, $month_names[3], 2021) ?>
>> ?>
>> >
>> > Would it be easier to just do
>> >
>> >     <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>
>> >
>> > .. and skip month_names[], its lookup, relying on the user to figure out
>> > how to "translate" "%1\$s %2\$s %3\$s", and documenting how to translate
>> it?
>>
>> Would this address Shin-Ichi's issue?
>>
>> -bill!
>>
>>
>> > On Fri, Mar 5, 2021 at 1:02 PM Bill Kendrick <nb...@so...> wrote:
>> >
>> > > On Thu, Mar 04, 2021 at 11:12:36AM +0100, Miguel Bouzada wrote:
>> > > > I saw that now it appears to translate "March" ... and the other 11
>> > > months?
>> > >
>> > > I think perhaps I should have them all ready for use in
>> > > pre-translated strings, like:
>> > >
>> > >   $month_names[] = array(
>> > >     "", /* zeroth */
>> > >     gettext("January"),
>> > >     gettext("February"),
>> > >     ...
>> > >     gettext("December")
>> > >   );
>> > >
>> > > And then use them in the documentation like so:
>> > >
>> > >   <?= sprintf(gettext("%1\$s %2\$s %3\$s"), 5, $month_names[3], 2021)
>> ?> ?>
>> > >
>> > > -bill!
>> > >
>> > > >
>> > > > O xov., 4 de mar. de 2021 as 07:56, Bill Kendrick (<nb...@so...>)
>> > > > escribiu:
>> > > >
>> > > > > On Tue, Mar 02, 2021 at 05:24:28PM +0900, TOYAMA Shin-ichi wrote:
>> > > > > > Hi,
>> > > > > >
>> > > > > > I have just finished working on "README".
>> > > > >
>> > > > > Thanks!
>> > > > >
>> > > > >
>> > > > > > While checking the generated html file, I found that notation for
>> > > > > > date and time look strange. For example at the release date on
>> > > > > > the topmost and at the example for the naming of PNG file.
>> > > > > >
>> > > > > > It seems that strftime() does not output strings in proper order
>> > > > > > at least for Japanese.
>> > > > >
>> > > > > Hrm, I wonder if it's an artifact of my laptop's configuration
>> > > > > (since that's where I run "make" which runs "php" to do all
>> > > > > of the work to generate the HTML).
>> > > > >
>> > > > >
>> > > > > > Then, I think it is more flexible for translators for various
>> > > > > > languages to simply separate Year, Month and Day as follows,
>> > > > > >
>> > > > > >   sprintf(gettext("%1\$s %2\$s %3\$s"), 21, gettext("February"),
>> > > 2021)
>> > > > >
>> > > > > Okay, thanks!
>> > > > >
>> > > > >
>> > > > > > One more thing,
>> > > > > >
>> > > > > > "msgid" for the following sentence looks missing.
>> > > > > >
>> > > > > > Save the picture in PNG format. It is highly recommended that you
>> > > name
>> > > > > the filename using the current date and time, since that's the
>> > > convention
>> > > > > Tux Paint uses:
>> > > > >
>> > > > > Hah!  Whoops, yes!  There were a _lot_ of strings to
>> > > > > wrap in gettext(), and I wanted to do it manually so
>> > > > > I could rewrite things here & there to try and consolidate
>> > > > > strings so there'd be a _few_ less to have to translate. :)
>> > > > >
>> > > > > Thanks for your keen eye!
>> > > > >
>> > > > > -bill!
>> > > > >
>> > > > >
>> > > > > _______________________________________________
>> > > > > Tuxpaint-i18n mailing list
>> > > > > Tux...@li...
>> > > > > https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > Membro do áGrupo de Amigos GNU/Linux de Pontevedra (GALPon)â
>> > > > http://galpon.org
>> > > > Membro de áProxecto Trasnoâ http://trasno.gal
>> > > > Co-coordinador do proxecto áGALPon MiniNoâ http://minino.galpon.org
>> > >
>> > >
>> > > > _______________________________________________
>> > > > Tuxpaint-i18n mailing list
>> > > > Tux...@li...
>> > > > https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
>> > >
>> > >
>> > > --
>> > > -bill!
>> > > Sent from my computer
>> > >
>> > >
>> > > _______________________________________________
>> > > Tuxpaint-devel mailing list
>> > > Tux...@li...
>> > > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>> > >
>>
>>
>> > _______________________________________________
>> > Tuxpaint-devel mailing list
>> > Tux...@li...
>> > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>>
>>
>> --
>> -bill!
>> Sent from my computer
>>
>>
>> _______________________________________________
>> Tuxpaint-devel mailing list
>> Tux...@li...
>> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>>
>---- inline file
>---- inline file
>_______________________________________________
>Tuxpaint-devel mailing list
>Tux...@li...
>https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel

-- 
TOYAMA Shin-ichi mailto:sh...@wm...

Re: [Tuxpaint-i18n] [Tuxpaint-devel] Migrating Tux Paint's docs to its own repo for PO (gettext) translation

[Mark K. <tux...@cb...>]

> > Would it be easier to just do
> >
> >     <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>
> >
> > .. and skip month_names[], its lookup, relying on the user to figure out
> > how to "translate" "%1\$s %2\$s %3\$s", and documenting how to
translate it?
>
> Would this address Shin-Ichi's issue?

It does, and the output does come out "correct" for all languages libc has
locale data for, but the European language output uses numerals instead of
the full month names which feels less polished.  So for US English it
outputs "01/30/2021" instead of "January 30, 2021", for French it outputs
"30/01/2021" instead of "30 janvier 2021", etc. C is the worst, outputting
"01/30/21" instead of something more sensible like "2021-01-30" (ISO
standard).

If we want the output to be correct for all languages by default but be
able to polish it up for some select languages something like this may be
reasonable:

<?= strftime(gettext("%x"), strtotime("2021-01-30")) ?>


... and let each language override "%x" (localized default) with "%e %B %Y"
("30 January 2021") or "%B %e, %Y" ("January 30, 2021) or "%F"
("2021-01-30").

If having gettext("%x") everywhere is a problem it can be wrapped with a
function like so once in include.php:

function localized_date($date) {
  return strftime(gettext("%x"), strtotime($date));
}


... then called like so from other php files:

<?= localized_date("2021-01-30") ?>


Mark

On Sun, Mar 7, 2021 at 1:25 AM Bill Kendrick <nb...@so...> wrote:

> On Fri, Mar 05, 2021 at 11:19:26PM -0500, Mark Kim wrote:
> > > <?= sprintf(gettext("%1\$s %2\$s %3\$s"), 5, $month_names[3], 2021) ?>
> ?>
> >
> > Would it be easier to just do
> >
> >     <?= strftime("%x", mktime(0, 0, 0, 3, 5, 2021)) ?>
> >
> > .. and skip month_names[], its lookup, relying on the user to figure out
> > how to "translate" "%1\$s %2\$s %3\$s", and documenting how to translate
> it?
>
> Would this address Shin-Ichi's issue?
>
> -bill!
>
>
> > On Fri, Mar 5, 2021 at 1:02 PM Bill Kendrick <nb...@so...> wrote:
> >
> > > On Thu, Mar 04, 2021 at 11:12:36AM +0100, Miguel Bouzada wrote:
> > > > I saw that now it appears to translate "March" ... and the other 11
> > > months?
> > >
> > > I think perhaps I should have them all ready for use in
> > > pre-translated strings, like:
> > >
> > >   $month_names[] = array(
> > >     "", /* zeroth */
> > >     gettext("January"),
> > >     gettext("February"),
> > >     ...
> > >     gettext("December")
> > >   );
> > >
> > > And then use them in the documentation like so:
> > >
> > >   <?= sprintf(gettext("%1\$s %2\$s %3\$s"), 5, $month_names[3], 2021)
> ?> ?>
> > >
> > > -bill!
> > >
> > > >
> > > > O xov., 4 de mar. de 2021 ás 07:56, Bill Kendrick (<nb...@so...>)
> > > > escribiu:
> > > >
> > > > > On Tue, Mar 02, 2021 at 05:24:28PM +0900, TOYAMA Shin-ichi wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I have just finished working on "README".
> > > > >
> > > > > Thanks!
> > > > >
> > > > >
> > > > > > While checking the generated html file, I found that notation for
> > > > > > date and time look strange. For example at the release date on
> > > > > > the topmost and at the example for the naming of PNG file.
> > > > > >
> > > > > > It seems that strftime() does not output strings in proper order
> > > > > > at least for Japanese.
> > > > >
> > > > > Hrm, I wonder if it's an artifact of my laptop's configuration
> > > > > (since that's where I run "make" which runs "php" to do all
> > > > > of the work to generate the HTML).
> > > > >
> > > > >
> > > > > > Then, I think it is more flexible for translators for various
> > > > > > languages to simply separate Year, Month and Day as follows,
> > > > > >
> > > > > >   sprintf(gettext("%1\$s %2\$s %3\$s"), 21, gettext("February"),
> > > 2021)
> > > > >
> > > > > Okay, thanks!
> > > > >
> > > > >
> > > > > > One more thing,
> > > > > >
> > > > > > "msgid" for the following sentence looks missing.
> > > > > >
> > > > > > Save the picture in PNG format. It is highly recommended that you
> > > name
> > > > > the filename using the current date and time, since that's the
> > > convention
> > > > > Tux Paint uses:
> > > > >
> > > > > Hah!  Whoops, yes!  There were a _lot_ of strings to
> > > > > wrap in gettext(), and I wanted to do it manually so
> > > > > I could rewrite things here & there to try and consolidate
> > > > > strings so there'd be a _few_ less to have to translate. :)
> > > > >
> > > > > Thanks for your keen eye!
> > > > >
> > > > > -bill!
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Tuxpaint-i18n mailing list
> > > > > Tux...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
> > > > >
> > > >
> > > >
> > > > --
> > > > Membro do «Grupo de Amigos GNU/Linux de Pontevedra (GALPon)»
> > > > http://galpon.org
> > > > Membro de «Proxecto Trasno» http://trasno.gal
> > > > Co-coordinador do proxecto «GALPon MiniNo» http://minino.galpon.org
> > >
> > >
> > > > _______________________________________________
> > > > Tuxpaint-i18n mailing list
> > > > Tux...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/tuxpaint-i18n
> > >
> > >
> > > --
> > > -bill!
> > > Sent from my computer
> > >
> > >
> > > _______________________________________________
> > > Tuxpaint-devel mailing list
> > > Tux...@li...
> > > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
> > >
>
>
> > _______________________________________________
> > Tuxpaint-devel mailing list
> > Tux...@li...
> > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>
>
> --
> -bill!
> Sent from my computer
>
>
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>