Hello,
On Thu, May 10, 2018 at 01:53:06PM -0400, Ineiev wrote:
> 5. Bump Savane version and send the new POT to TranslationProject.
> 6. Get updated translations from TranslationProject and actually
> enable i18n.
I've sent the new POT to the TP; meanwhile, I installed an updated
Russian translat
Hello,
On Thu, May 10, 2018 at 01:53:06PM -0400, Ineiev wrote:
>
> 4. Add a page where users can select language (possibly overriding
> their browser preferences).
I've implemented this, the new page is /i18n.php; the link to it
and all translations are still disabled. the link will be located
i
Ineiev wrote:
> I've just pushed the rest of my i18n branch to master and
> installed it. the next steps are going to be:
>
> 4. Add a page where users can select language (possibly overriding
> their browser preferences).
> 5. Bump Savane version and send the new POT to TranslationProject.
> 6. G
Hello,
I've just pushed the rest of my i18n branch to master and
installed it. the next steps are going to be:
4. Add a page where users can select language (possibly overriding
their browser preferences).
5. Bump Savane version and send the new POT to TranslationProject.
6. Get updated translati
On Sun, Jul 16, 2017 at 01:14:58PM -0400, Ineiev wrote:
>
> I've just pushed i18n-2017-07-13-bis: just merged the fixes and added
> more detailed commit logs.
Pushed to master and installed; now I'm going to add README files to
'administration' web pages repository saying that they are obsolete.
On Sat, Jul 15, 2017 at 07:58:54AM -0400, Ineiev wrote:
> > 5.
> > There are several very large commits titled "review localized strings",
...
> > It would be easier to understand if those were broken down per topic
> > (i.e. if "localization" - then only touching lines that actually
> > use locali
On Fri, Jul 14, 2017 at 09:50:13PM -0400, Assaf Gordon wrote:
>
> If I may suggest/comment on few things:
Thanks!
> 1.
> This commit introduces a $GLOBAL variable:
> https://git.savannah.gnu.org/cgit/administration/savane.git/commit/?h=i18n-2017-07-13&id=ea1a4f617e8e7f30f1a693da9b4a67ef941ff312
Hi,
> On Jul 14, 2017, at 02:34, Ineiev wrote:
>
> I haven't reviewed i18n of all frontend sources, but the branch
> has grown long enough, and it contains some changes unrelated to
> i18n itself (most notably, preview for tracker comments); so
> I'd like to fast-forward master to i18n-2017-07-1
Hello,
I haven't reviewed i18n of all frontend sources, but the branch
has grown long enough, and it contains some changes unrelated to
i18n itself (most notably, preview for tracker comments); so
I'd like to fast-forward master to i18n-2017-07-13 and install it.
signature.asc
Description: Digit
On Tue, Jun 20, 2017 at 03:03:19AM -0400, Ineiev wrote:
>
> I attach a tentative patch against current HEAD for the reference.
Actually attaching.
0001-import-webpages.patch.gz
Description: Binary data
signature.asc
Description: Digital signature
Hello,
Savane has been registered on the TranslationProject; now missing
parts of its user interface should be made localizable.
I'd like to start with what currently is maintained
as 'administration' 'web pages'. in theory, people can add
localized versions of those files right to that CVS repos
Hello,
I'd like to work on enabling i18n support of Savannah.
I think in the short run it will amount in committing
some updates like pulling a newer po.m4 from gettext,
extracting new messages, registering it on TranslationProject.
Any stoppers?
signature.asc
Description: Digital signature
12 matches
Mail list logo
