>
> I'm very happy that someone else started translating this awkward text
> file.
Lol, i've read a little about reStructuredText from some quick tutorial I
found on the web and found it, not that hard to understand. For now, only
the underlines are a little boring to get right...
As the matter of fact, I stopped working on this file for now (since
> Thunderbird 3.0.5 project was finally done with my friends as the date, if
> you look for one).
> I even threw away all my work - as I thought it's worthless. Finally, I
> think that everyone should take into account that we have on Earth around
> 6700 natural languages (not to count esperanto and all alike).
You're quitting? :( Why? I can see the effort required for this but don't
believe it to be meaningless.
So, we need to agree that essential part or survival guide in help must be
> left UNTRANSLATED (=in English?). Behind that Survival part/Quick guide
> (containing quick and very brief guide around menus, plugins and so forth),
> the it comes all about in your mothers, fathers or another spoken/written
> language.
> That's what I think about the help and what it should be like. :)
>
I disagree.
It's obvious that the documentation (and even Geany itself) will hardly be
translated to the 6700 existing languages you refer.
But that argument is also valid to Geany's interface...yet there are
translations for it.
IMHO, if a user sees that Geany is available in Portuguese (has an example)
and he wants to use it in Portuguese, I doubt he will like to click a menu
and start seeing things in English.
He may not even know any english...So having the interface and documentation
in Portuguese will help a lot.
That said, I can't see why is there a need to not translate something...
Out of curiosity is it hard to make F1 point to the correct help file
according to Geany's localization? (From a developer point of view)
Kind Regards,
André
Due to the *Jože Klepec *email back in April I started making the
documentation translation to Portuguese.
This requires indeed a great effort but I believe it to be very useful.
I started by using OmegaT which seems easy enough to understand and the
translation memory helps a little...
I also like the google translator integration.
However I'm writing not only to share this facts but more to share problems
and solutions.
1) I felt the need to change the segmentation settings of OmegaT, more
precisely I unset the "Text files segmentation" rule so it became an
exception.
This rule breaks sentences and paragraphs each time a newline is detected.
And geany.txt has newlines in the middle of phrases which was making the
translation impossible.
Are these newlines in geany.txt required for some kind of text formatting?
They seem to limit the width of the text but I doubt this has to be made
manually.
2) So far, the setting change in 1) had one negative side effect. I'm unable
to have the first table right.
The images attached show the 2 types that come out after a series of tries.
If I edit the html file to include <br> after each authors name, the table
gets equal to the original one.
Any thoughts on how to solve this?
3) I've been generating the html by explicitly writing *rst2html -stg
--stylesheet=geany.css ./geany.txt geany.html* this is because running *make
doc* inside the geany's doc directory gives me the *make: *** No rule to
make target `doc'. Stop.* error.
I'm not sure but I see that in the doc folder there is only the Makefile.am
and Makefile.in, in "my days" the make tool looked for a Makefile file,
without any extension. Times change and I probably didn't get the memo :p.
(I don't write a makefile in quite some time...)
Where's the problem?
4) I noticed 1 typo in geany.txt and made a little change (added a period to
a sentence) to have the correct behaviour out of OmegaT.
I'm thinking, in the end, of sending a patch with the changes I make.
It's the most practical thing right? Or I shouldn't touch geany.txt at all?
Kind Regards,
André Glória
I tried Lucas Vieites (thanks) suggestion and the problem was no more.
Next time i'll remember trying it out :).
So I investigated a little more and found the culprit, a lonely argument
(see screenshoot pls).
Don't know how it got there alone...
@Frank, I tried to find Lex's email about the build menu entries but had no
luck.
As a side discovery Lex writes very long emails :p
Kind Regards
André
I don't know if I should be reporting this here, but it's translation
related.
In the build menu information about the translation file is appearing and I
believe it shouldn't.
The attached screen-shoot explains it better than words.
I tested with pt_PT, pt_BR, de_DE, en_GB and en_US, by executing geany from
the console with *LANG=pt_PT.utf-8 geany*
Only in the latter (en_US) there isn't any problem.
Kind Regards,
André
Ps: Thanks for the "Add custom filetypes features" I have some friends that
will be changing to Geany because of that.
Hi all,
we are happy to announce a new release of Geany!
For a comprehensive list of changes in Geany 0.19, please see
Release Notes. A very detailed and complete list of changes can be
found in the ChangeLog.
Some of the highlights:
* Build system reworked to be much more configurable (by Lex Trotman).
* Use POSIX system/GNU regex engine for find & replace. This alters
regex syntax - we now support '?' operator and match newlines.
* Support adding custom filetype files.
* Add preference and support for virtual spaces.
* New filetypes: Txt2Tags, Abc, Verilog, Genie.
* Add new special template wildcard "{command:...}" to use the output
of a shell command in templates.
* Allow '+<number>' and '-<number>' as values for Goto Line inputs to
jump relative to the current line.
* Add 'View->Editor->Color Schemes' menu (only shown if color scheme
files exist).
* Add word part autocompletion for the current selected item when
pressing keybinding (default Tab) - Enter still completes normally.
* Improvements in symbol parsing of D, Java, PHP, Perl, Python, R, VHDL.
* Support {ob}, {cb} and {pc} to escape wildcard strings with {, },
% for snippets, fileheader and file templates.
* Add {project}, {description} template wildcards (#2954737).
* Added translations: ast
* Updated translations: de, en_GB, es, fr, gl, ja, nl, pt, ru, sl, sv,
tr, vi, zh_CN.
We want to thank all translators who have updated their translations in
this release as well as all people who contributed to this release
with patches, feedback, bug reports and so on.
Thank you!
All downloads can be found on http://download.geany.org.
Happy updating,
Enrico
Hi translators and friends of Geany,
Short after announcement of string freeze for Geany, I'm happy we also
have a string freeze for the combined Geany-plugins project which is
also planned to be released in about 2 weeks.
As before, I'd be very happy if you could send a patch or complete file
with translation to either the geany-i18n mailing list or direct to me
within the next two weeks so we can include it to the next release.
Deadline will be 2010-06-02.
To make it more easy for you I've already uploaded updated versions of
the po files to svn with r1395. You can access them as always at
http://geany.svn.sourceforge.net/viewvc/geany-plugins/trunk/geany-plugins
or by checking out the svn tree of Geany by using e.g.
svn co https://geany.svn.sourceforge.net/svnroot/geany-plugins/trunk/geany-plugins geany-plugins
Fans of git can also use the interface provided by http://git.geany.org
by using
git clone http://git.geany.org/git/geany-plugins
Also at http://i18n.geany.org/plugins are statistics and daily updated
files available.
As mentioned before, we are trying to have all translations complete by
2010-06-02.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to translate
same things two or three times. Also please feel to ping me for every
question or if you like to start a new translation for an unsupported
language.
Thanks and happy translating ;)
Frank
--
Frank Lanitz <frank(a)frank.uvena.de>
>
> (it's a shame,
>
but I know some "technical stuff" better in english than in my own
> language, lol)
>
I don't believe it to be a shame. It happens to me also so, you're not alone
;).
It's hard to translate technical terms that you use in a daily basis in
their untranslated version...
Kind Regards,
André
Hi translators and friends of Geany,
After a long time I'm glad to finally announce string freeze for Geany
0.19 which is planned to be released in about 2 weeks.
I'd be very happy if you could send a patch or complete file with
translation to either the geany-i18n mailing list or direct to me
within the next two weeks so we can include it to the next release.
Deadline will be 2010-06-02.
To make it more easy for you I've already uploaded updated versions of
the po files to svn with r4948. You can access them as always at
http://geany.svn.sourceforge.net/viewvc/geany/trunk/po/
or by checking out the svn tree of Geany by using e.g.
svn co https://geany.svn.sourceforge.net/svnroot/geany/trunk geany
Fans of git can also use the interface provided by http://git.geany.org
by using
git clone http://git.geany.org/git/geany
Also at http://i18n.geany.org/ are statistics and daily updated
files available.
As mentioned before, we are trying to have all translations complete by
2010-06-02.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to translate
same things two or three times. Also please feel to ping me for every
question or if you like to start a new translation for an unsupported
language.
Thanks and happy translating ;)
Frank
--
Frank Lanitz <frank(a)frank.uvena.de>
On Thu, 6 May 2010 16:10:40 +0100, Nick wrote:
> Hi all,
> Just a quick mail to let everyone know we're planning to make a Geany
> 0.19 release once everything is ready. We're thinking of early June
> but this may change ;-)
I didn't manage to make the release this weekend (problems with my
internet connection) and so I'd like to delay the release to next
weekend (Saturday, June 12th).
If any translators were too late, this is your chance :).
Sorry to all other translators who tried to get it ready in time. Thank
you very much for your efforts!
Regards,
Enrico
--
Get my GPG key from http://www.uvena.de/pub.asc