(
Jump to the original submission)
Sat 17 Nov 2012 08:49:17 AM UTC, comment #7:
Thank you, fixed.
|
Sat 17 Nov 2012 08:25:23 AM UTC, comment #6:
http://gnu.org/s/gnun/reports/
Very useful, thanks. Note this:
[es] Esperanto
--
Dora Scilipoti
GNU Education Team
http://www.gnu.org/education
|
Fri 16 Nov 2012 09:23:06 AM UTC, comment #5:
I've just setup a cron job with initial version of reports
maintained in http://gnu.org/s/gnun/reports/
(I didn't use trans-coord web pages because their changes
are nofified to trans-coord-devel@).
A link to the specific report page could be added
to generic.$lang.html, but probably it would better
dwell on team's homepage.
|
Fri 09 Nov 2012 09:25:26 AM UTC, comment #4:
If this is about tracking, I'd suggest a separate
per-team page displaying status of translations, updated by
a GNUN cron job e.g. somewhere in http://gnu.org/s/trans-coord/.
Once rms advised against linking to PO files from http://www.gnu.org
pages (when out-of-date notices were discussed);
and indeed, adding another link wouldn't be very good for
the visitors, to say nothing of the difficulty to implement
such links on all pages.
|
Wed 07 Jul 2010 12:15:22 AM UTC, comment #3:
Having it after "back to top" doesn't sound right.
replacing the "Please see the <Translations README>..." paragraph in the boilerplate with an SSI include sounds like the right thing to do. It means a zillion changes now, but then at least future changes will only have one source. I don't think that paragraph ever intentionally varies, does it?
No other ideas come to mind. Sorry. Good luck with the SSI-fu.
|
Mon 05 Jul 2010 08:06:19 PM UTC, comment #2:
Hmm. Actually, a new SSI include is not an option, as this would imply modifications to every article anyway...
So the only way to avoid this seems to be to add this link after the "back to top" link in server/footer-text.html. Not very appealing.
|
Mon 05 Jul 2010 07:59:40 PM UTC, comment #1:
I agree with you that this looks like a nice addition. But I can't see a way to do it via gnun, at least if we insist on something reliable, automatically updated and translatable. We need to discuss a possible solution with the webmasters.
It would be rather undesirable to add new snippet to every webpage; this means hundreds of modifications. IMHO the best is to encapsulate the common code in a separate include file (together with "Please see the Translations README...", then with some violent SSI-fu (#if expr=..., etc...) to determine automatically the link at serve time.
Webmasters, WDYT? If it appears the correct approach to implement this, I'll see what I can do...
|
Mon 05 Jul 2010 06:09:13 PM UTC, original submission:
It would be nice to have a "Download po file" link just after. "Please see the Translations README for information on coordinating and submitting translations of this article." for translators. It would make it easier for translation team members to inspect status of specific translations instead of tracking the whole repository via (we have many people in our translation team and it would help people to take responsibility for specific pages).
We can expect a coordinator to know and be able to use CVS, but if that barrier can be reduced a bit for other team members, it would be helpful for many non technical users who would like to participate but are not able to cope with a version control system (I know there is a plan for integrating a web based translation system but this would be a small step without much efforts). Anyway it is an extra barrier which we could easily do away.
PS: Consider vertimus also as a candidate - it is used by gnome (l10n.gnome.org)
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Follow 14 latest changes.
| Date |
Changed By |
Updated Field |
Previous Value |
=> |
Replaced By |
| Tue 11 Dec 2012 02:19:30 PM UTC | ineiev | Status | Ready For Test |  | Works For Me |
| | | Open/Closed | Open |  | Closed |
| Tue 11 Dec 2012 02:18:22 PM UTC | ineiev | Carbon-Copy | Removed 71509 |  | - |
| Sat 17 Nov 2012 08:49:17 AM UTC | ineiev | Assigned to | yavor |  | ineiev |
| Fri 16 Nov 2012 10:16:33 AM UTC | ineiev | Carbon-Copy | Removed 685 |  | - |
| Fri 16 Nov 2012 10:16:26 AM UTC | ineiev | Carbon-Copy | Removed 43892 |  | - |
| Fri 16 Nov 2012 09:24:28 AM UTC | ineiev | Carbon-Copy | Removed -unavailable- |  | - |
| Fri 16 Nov 2012 09:24:09 AM UTC | ineiev | Carbon-Copy | Removed -unavailable- |  | - |
| Fri 16 Nov 2012 09:23:06 AM UTC | ineiev | Status | In Progress |  | Ready For Test |
| Mon 05 Jul 2010 07:59:40 PM UTC | yavor | Severity | 3 - Normal |  | 1 - Wish |
| | | Status | None |  | In Progress |
| | | Assigned to | None |  | yavor |
| | | Carbon-Copy | - |  | Added -unavailable- |
| Mon 05 Jul 2010 06:09:13 PM UTC | praveen_a | Carbon-Copy | - |  | Added -unavailable- |