Od: <blue...@centrum.cz>
Komu: Antonio Scuri <antonio.sc...@gmail.com>
Datum: 27.09.2017 19:46
Předmět: Re: IUP contribution: Czech localization + improved localization
scheme + bug fixes
Od: Antonio Scuri <antonio.sc...@gmail.com>
Komu: blue...@centrum.cz
> Datum: 22.09.2017 19:55
> Předmět: Re: IUP contribution: Czech localization + improved localization
>
CC: <i...@tecgraf.puc-rio.br, Iup-users@lists.sourceforge.net>
Hi,>> First of all thank you for your contribution. >> About 1) and 3):>The
first commit is just the Czech localization in the current scheme (similarto the Spanish one).
It doesn't bring any structure changes. I guess it could becommitted right away (before the
other change is decided).
> Large scale modifications in IUP code will be more effective if we work together. Your modifications are interesting but I can not use it. They add a dependency to Linux tools to the Makefile that directly affect the Windows build. >> I have an alternative that is more IUP friendly. The IupSetLanguagePack function accepts a IupUser element that can contain the string translations. This can be stored in a LED, Lua or C files. And directly loaded by IUP, no need for external tools. But we didn't have an fully complete example. So I downloaded your CZECH lang file and converted to the LED format. Notice that LED and Lua can also be converted to C files to embed in the application code.>> Attached the CZECH utf8 file in LED and C format. Please take a look.>As far as the localization scheme is concerned, I kind of expected that sed and awkis available in Windows too (as part of Cygwin or Mingw).But if they are not a hard dependency, I would say the same script can be codedin
Windows as a batch script. (And called from tecmakewin.mak - this is the makefileused in Windows, right?).I looked at IupSetLanguagePack() function. It is a good functionality. It might beused here. However, it won't help much. I mean, the main selling points for thechange was:1. separate language strings from code2. use very simple text files (easy for translation), without any code/syntax suger3. let the machines generate the code without the need for manual maintenanceUsing the LED file, would fulfill 1) and partly also 2).But the files would have to be distributed and loaded at runtime, which is not optimal.When using ledc compiler, we have the same situation as in my suggested solution,i.e. there is a need to transform an input file to a output C source.
So, I think that having a script that is called from make is a good solution. The questionis what tool/language to use. Dual awk (unixes)
and batch (Windows) could work fine.Or use a Lua script? Is Lua currenly required or not?> About 2):> Unfortunately we used
"box" when we mean "frame", but for coherence with the attribute names, we have to maintain the name "box"
where we used. The Spanish translation was actually incorrect, when it used "cuadro". So there is no need for another definition
for now.>I am afraid I don't understand what you mean by "coherence". I thought that IUP_* variablesare not exposed in API
and can be easily changed. Actually, the names are quite generic andthat might lead to their usage for ambiguous stuff. It seems to me
that e.g. plot marks wouldbe better named as IUP_PLOT_MARK_CIRCLE, IUP_PLOT_MARK_BOX, .... AlsoIUP_CANCEL would be better as
IUP_BUTTON_CANCEL, etc.As for IUP_BOX, it appears in two places. When I edit a plot, I can see a awkward descr
iptionin one of the places (either as plot mark, or frame around the plot).
> About the bug-fixes, I committed all of them. Thanks.Thanks for that.It seems to me
that you may copy the changes manually, because there are not the originalcommit messages
(they contain useful info sometimes).Note that it is possible to download github commits by
adding ".patch" to the URL [1]. Then the patch could be easily added to SVN. But I
don't know whether there is a tool to also includeoriginal commit message, or it has to be
added manually.
[1]
https://stackoverflow.com/questions/21903805/how-to-download-a-single-commit-diff-from-github>
Regarding the GIT, we are a very small team, so keeping a mirror is not in our
plans. I know it is more popular, but for now we are going to keep just the SVN. But
feel free to mirror it anywhere. If I recall right there is already some mirror
around, can't remember where.> I tried the issue tracker in the past, but it was
so much work for us with not much benefit that I give up. So our discussion tool is
this email list. Or you can send email directly to me.I don't know sourceforge much,
but I understand that it could be a administrative overhead.
As for the git mirrors, they are on github under svn2github
account:https://github.com/svn2github/imtoolkit-imhttps://github.com/svn2github/canvasdraw-cdhttps://github.com/svn2github/iup-githubI
use their forks in my blueowl04 account to be able to commit to them.> Best
Regards,> Antonio ScuriPS: resending the message after the error:
Iup-users@lists.sourceforge.net SMTP error from remote mail server after RCPT
TO:<Iup-users@lists.sourceforge.net>: host sfs-lb-ml.v29.ch3.sourceforge.com
[172.29.29.17]: 550 Unknown user
2017-09-20 13:16 GMT-03:00 <blue...@centrum.cz <blue...@centrum.cz>>:
Hello Antonio,
some time ago I came across IUP. I started to play with it a bit.
I found the toolkit very nice, mainly due to its simplicity and plain C API.
Also
integrated Lua binding is a great feature.
I decided to contibute to the project to make it even better. As a start, I have
made Czech localization (my native language). And because I found the current
localization framework not much flexible and scalable, I made an enhancement
to it too.
I placed the code to my github repo, which is forked from unofficial github
clone
(thanks to great svn2github service).
https://github.com/blueowl04/iup-github/commits/localize-czech
<https://github.com/blueowl04/iup-github/commits/localize-czech>
The localize-czech branch contains 3 commits:
1. Add support for CZECH language
2. Don't use IUP_BOX ambiguously, split it to IUP_MARK_BOX and IUP_BOX
3. Make localization easier and more flexible
In bug-fixes branch, I also published a few bugfixes, including one crash
I encountered.
https://github.com/blueowl04/iup-github/commits/bug-fixes
<https://github.com/blueowl04/iup-github/commits/bug-fixes>
Notes:
* Unfortunatelly, your sourceforge SVN repository doesn't have an issue tracker.
Please consider adding the tickets system, that would allow managing issues,
including patches, etc. And a discussion tool would be good too.
* It would be nice if the project had an official github mirror. Many people use
git these days and it would certainly help to popularize the project.
Best Regards
Jiří Klimeš
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users
