Bug 516117 - Add publican module to Fedora's Transifex instance at translate.fedoraproject.org
Summary: Add publican module to Fedora's Transifex instance at translate.fedoraproject...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 1.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Fedora Extras Quality Assurance
URL: http://translate.fedoraproject.org
Whiteboard:
Depends On: 527327
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-06 19:43 UTC by Karsten Wade
Modified: 2010-11-24 04:18 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-13 11:53:47 UTC
Embargoed:


Attachments (Terms of Use)

Description Karsten Wade 2009-08-06 19:43:49 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Karsten Wade 2009-08-06 19:47:10 UTC
Sorry about the double-tap, here's the real request.

Can we coordinate with Fedora L10n to get publican added as a module in Fedora's Transifex instance?

https://translate.fedoraproject.org

In addition to general l10n for Publican, we may want to translate parts of the content in brand-specific modules.

Should I file a separate bug for publican-fedora to be added, or can this one bug cover it all?

Comment 2 Jeff Fearn 🐞 2009-08-11 00:51:38 UTC
One bug is fine, we will probably use components for the brands and such.

I will get on to this when I get back from holidays, after the 24th August.

Comment 3 Jeff Fearn 🐞 2009-09-30 04:57:55 UTC
It turns out that the current install of transifex at https://translate.fedoraproject.org/ is too old to support multiple files per language, so this ticket will have to wait until after that site is updated.

The site is version 0.5.2 and multi-file support was added in version 0.6

It also occurs to me that transifex is setup to support the POSIX locales used by gettext (ISO 639 and ISO 3166 joined with an underscore), but publican, being and XML processing tool, uses RFC 4646 for language identification. This is probably going to cause problems.

Cheers, Jeff.

Comment 4 Ruediger Landmann 2009-09-30 05:06:15 UTC
(In reply to comment #3)

> It also occurs to me that transifex is setup to support the POSIX locales used
> by gettext (ISO 639 and ISO 3166 joined with an underscore), but publican,
> being and XML processing tool, uses RFC 4646 for language identification. This
> is probably going to cause problems.

This was fixed in more recent versions of Transifex (0.7?) -- it now supports the BCP 47/RFC 4646 codes too: http://transifex.org/changeset/780

Comment 5 Jeff Fearn 🐞 2009-09-30 20:56:25 UTC
(In reply to comment #4)
> (In reply to comment #3)
> 
> > It also occurs to me that transifex is setup to support the POSIX locales used
> > by gettext (ISO 639 and ISO 3166 joined with an underscore), but publican,
> > being and XML processing tool, uses RFC 4646 for language identification. This
> > is probably going to cause problems.
> 
> This was fixed in more recent versions of Transifex (0.7?) -- it now supports
> the BCP 47/RFC 4646 codes too: http://transifex.org/changeset/780  

Ah, very cool!

Looks like it was 0.7 http://docs.transifex.org/releases/0.7.html

Comment 6 Piotr Drąg 2010-03-12 15:59:18 UTC
I've added Common Content for Publican and publican-fedora. Now we should enable translation submission. Could you add transif user to appropriate FAS group?

https://translate.fedoraproject.org/projects/p/publican/

Comment 7 Ruediger Landmann 2010-03-13 01:56:16 UTC
(In reply to comment #6)
> I've added Common Content for Publican and publican-fedora. Now we should
> enable translation submission. Could you add transif user to appropriate FAS
> group?

Thanks Piotr -- User transif is already part of group svnpublicn

Comment 8 Piotr Drąg 2010-03-13 11:53:47 UTC
Submission to Common_Content and fedora-brand has been enabled. Thanks!


Note You need to log in before you can comment on or make changes to this bug.