Is detail information on strings available in Zanata online editor?
by Tiansworld
Hello everyone,
Recently I am updating the translation of anaconda on fedora.zanata.org. I
can't find any detail information about the string I'm translating. For
example, where does the string locate. This feature is called *occurrences*
in transifex. It tells the translator where the string comes from, in which
line, in which file.
This is really helpful when translators aren't sure about how to translate
the string. Then they can look up it in the original file to see the
context around it.
So could anyone tell me does Zanata have this feature? If it doesn't have,
would the Zanata project consider to implement it?
This message is CCed to g11n(a)lists.fedoraproject.org too.
--
Regards,
Tian Shixiong
Fedora Project Contributor
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 3 months
Minutes of G11N meeting 2016-01-20
by pravin.d.s＠gmail.com
Hi all,
Minutes are as follows
=====================
#fedora-meeting: g11n
=====================
Meeting started by pravins at 06:00:09 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2016-01-20/g11n.2016-01-2...
.
Meeting summary
---------------
* agenda and roll call (pravins, 06:00:22)
* LINK: https://fedoraproject.org/wiki/I18N/Meetings/2016-01-20
(pravins, 06:00:22)
* Upcoming schedule (pravins, 06:01:46)
* 2016-01-26 Change Checkpoint: Proposal submission deadline
(System Wide Changes) (pravins, 06:01:51)
* not scheduled yet Side Tag Builds Deadline (pravins, 06:01:51)
* not required Mass Rebuild (pravins, 06:01:51)
* 2016-01-26 Mass Rebuild (pravins, 06:01:52)
* 2016-02-16 Branch Fedora 24 from Rawhide (Rawhide becomes future
F25) (pravins, 06:01:52)
* 2016-03-01 Alpha Freeze (*) (pravins, 06:01:52)
* 2016-03-01 Software String Freeze (pravins, 06:01:54)
* 2016-03-01 Change Checkpoint: Completion deadline (testable)
(pravins, 06:01:56)
* 2016-03-01 Bodhi activation point (pravins, 06:01:58)
* 2016-03-15 Alpha Release (pravins, 06:02:00)
* Outstanding task (pravins, 06:03:59)
* #1: G11N infrastructure requirements (pravins, 06:03:59)
* LINK: https://fedorahosted.org/G11N/ticket/1 (pravins, 06:03:59)
* LINK: https://fedoraproject.org/wiki/G11N (pravins, 06:04:52)
* LINK: http://www.slideshare.net/ (pravins, 06:06:40)
* ACTION: pravins noriko to upload G11N slidedesk to slideshare and
link on Wiki. (pravins, 06:07:46)
* ACTION: ping Michelle for G11N Forum point in Wiki. (pravins,
06:10:06)
* IDEA: We can do some L10N pages cleanup at DevConf 2016 (pravins,
06:18:50)
* IDEA: Put wiki clean-up activities to respective language teams
hand. (pravins, 06:38:27)
* #5: Fedora L10N sprint (pravins, 06:40:39)
* LINK: https://fedorahosted.org/G11N/ticket/5 (pravins, 06:40:40)
* IDEA: L10N sprint between String Freeze and Translation deadline.
(pravins, 06:50:08)
* IDEA: Arrange badges for members contributing during L10N sprint
(pravins, 06:50:41)
* #57: Fedora 24 change planning (pravins) (pravins, 06:51:34)
* LINK: https://fedorahosted.org/i18n/ticket/57 (pravins, 06:51:34)
* #58: Prioritizing bugs for Fedora 24 release (pravins) (pravins,
06:58:21)
* LINK: https://fedorahosted.org/i18n/ticket/58 (pravins, 06:58:21)
* LINK:
https://fedoraproject.org/wiki/G11N/Fedora_24_G11N_Enhancements
(pravins, 06:59:08)
* #59: tracking of translation string changes (petersen) (pravins,
07:04:50)
* LINK: https://fedorahosted.org/i18n/ticket/59 (pravins, 07:04:50)
* #17: Live media with langpacks included (pravins, 07:07:38)
* LINK: https://fedorahosted.org/G11N/ticket/17 (pravins, 07:07:38)
* #36: gnome redesign plans for control-center Region and Languages
(anishpatil) (pravins, 07:09:09)
* LINK: https://fedorahosted.org/i18n/ticket/36 (pravins, 07:09:09)
* ACTION: anish_ to update ticket #36 with latest information.
(pravins, 07:10:45)
* Open Floor (pravins, 07:11:08)
* LINK:
http://fedoramagazine.org/globalization-test-days-report-fedora-23/
(pravins, 07:13:20)
* LINK:
https://fedoraproject.org/wiki/Test_Day:2015-08-18_L10N?rd=/Test_Day:2015...
(pravins, 07:14:06)
Meeting ended at 07:18:27 UTC.
Action Items
------------
* pravins noriko to upload G11N slidedesk to slideshare and link on
Wiki.
* ping Michelle for G11N Forum point in Wiki.
* anish_ to update ticket #36 with latest information.
Action Items, by person
-----------------------
* noriko
* pravins noriko to upload G11N slidedesk to slideshare and link on
Wiki.
* pravins
* pravins noriko to upload G11N slidedesk to slideshare and link on
Wiki.
* **UNASSIGNED**
* ping Michelle for G11N Forum point in Wiki.
* anish_ to update ticket #36 with latest information.
People Present (lines said)
---------------------------
* pravins (163)
* aeng (41)
* noriko (38)
* juhp (20)
* mfabian (10)
* zodbot (9)
* zoltanh7211 (7)
* apeter (6)
* fujiwarat (4)
* paragan (2)
* tagoh_ (1)
* ueno (1)
* epico (1)
* suanand (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Regards,
Pravin Satpute
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 3 months
Fedora Globalization meetup in Dev Conf 2016
by pravin.d.s＠gmail.com
Hi All,
* Most of the things have been done for my attendance to Dev Conf 2016. [1]
* Noriko is also travelling same time.
* If i remember correctly Zoltan is also travelling for Dev Conf.
* Mike Fabian from i18n team will be also there.
* Anyone else??
Also more members from Ambassadors group and also from council will be there.
Can we propose small meetup around couple of hours and touch up F24
pending task and other topics?
Regards,
Pravin Satpute
1. http://devconf.cz/
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 3 months
Next meeting focused on Localization+Zanata, WhenIsGood?
by pravin.d.s＠gmail.com
Hi All,
We are fast approaching deadline for planning phase of Fedora 24[1]
, few plans are already available on Wiki [2] also we have few tickets
open on Trac [3]
And also, lets discuss issues with G11N from L10N perspectives (Need
ticket for it)
Please add more items to piratepad [4], will move it to Wiki before meeting.
In this language computing group, we have active people from all
over world and finding suitable time to suit everyone is tricky.
Please select your suitable time on WhenisGood [5], do suggest if we
can add more options in it. Hint [6]
Best Regards,
Pravin Satpute
1. https://fedoraproject.org/wiki/Releases/24/Schedule
2. https://fedoraproject.org/wiki/G11N/Fedora_24_G11N_Enhancements
3. https://fedorahosted.org/G11N/report/1
4. http://piratepad.net/l10n-zanata
5. http://whenisgood.net/d5xy7ri
6. http://www.worldtimebuddy.com/?pl=1&lid=2174003,7284824,524901,1275339&h=...
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 3 months
Fwd: #59: tracking of translation string changes
by pravin.d.s＠gmail.com
fyi..
---------- Forwarded message ----------
From: Fedora Internationalization <i18n(a)lists.fedoraproject.org>
Date: 6 January 2016 at 12:36
Subject: #59: tracking of translation string changes
To:
#59: tracking of translation string changes
-----------------------+-------------------
Reporter: petersen | Owner: i18n@…
Type: task | Status: new
Priority: major | Keywords:
Blocked By: | Blocking:
-----------------------+-------------------
= description =
During the G11n FAD in Tokyo, we came up with the idea of tracking string
changes in Fedora to help catch string breakage and get some visibility on
translation status. Initially we would probably target only upstream
projects that are translated in Fedora Zanata for each Fedora release.
= reason =
Currently we have no direct way of knowing when strings change or break
the freeze in Fedora etc. This is valuable information for the L10n and
QA teams, and useful others too.
= recommendation/goal =
Create a tool/webapp to track translation in Fedora/Zanata.
For example it might compare what is in Zanata or Fedora packages vs what
is upstream in Github etc, and alert/flag
packages that need new strings to be pushed to Zanata or that have
translations to be pulled upstream from Zanata.
--
Ticket URL: <https://fedorahosted.org/i18n/ticket/59>
Fedora Internationalization <http://fedorahosted.org/i18n/>
Fedora i18n Project
--
i18n mailing list
i18n(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/i18n
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 3 months
Re: Zanata asking Fedora users to provide name, userid and email even
after FAS openid login
by pravin.d.s＠gmail.com
On 17 November 2015 at 08:41, Noriko Mizumoto <noriko(a)fedoraproject.org>
wrote:
> On 2015年11月07日 00:11, pravin.d.s(a)gmail.com wrote:
> > Hi All,
> >
> > $subject. Two problems:
> >
> > 1. There is chance of FAS user can create account with different
> > username and it will affect our plan to connect with FedBus and generate
> > stats.
>
> This applies to first time login to fedora.zanata.org with FAS username,
> right?
Yes.
> What is FedBus?
>
FedBus is where all activity messages related Fedora get listed.
>
> >
> > 2. Was talking with CLA agreement with Zanata guys earlier. They said
> > rather than they work on signing agreement from users, they want user
> > simply sign CLA of different project i.e. Fedora, OepnStack and they
> > will simply connect users to respective project portal. In this case no
> > need to sign other terms of Zanata (please correct me here if i am
> > wrong). I mean just user can simply log in and start work.
>
> This is current state implemented where Fedora new translator is
> required to sign Fedora Project Contributor Agreement (not CLA), before
> login and join corresponding team in zanata.
>
> If zanata can check whether new user attempting first login has already
> obtained FPCA or not, and then can accept or reject login accordingly,
> it will be great help for all language team coordinators. Currently the
> coordinators manually check this.
>
If its possible to check, then it is fine.
Else lets have a simple checkbox after user logs in.
Any progress here?
Let me know if anything need to do from my side.
Regards,
Pravin Satpute
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
8 years, 3 months
