Opened 9 years ago

Closed 8 years ago

Last modified 3 years ago

#2713 closed defect (fixed)

need to order pages in transifex by priority

Reported by: arma Owned by: runa
Priority: Medium Milestone:
Component: Community/Translations Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now the man pages are near the top of the list of pages at
https://www.transifex.net/projects/p/torproject/
And it's caused us to get arabic man pages but no arabic front page.

This is waste of time both for us and for our volunteer translators.

What are some options for hacking something together while we wait for Transifex to decide it's a feature they should offer?

E.g., remove all the pages and add them back in in reverse order?

Or maybe sub-projects by priority and point people to the subproject that contains only high priority pages?

Child Tickets

Change History (10)

comment:1 Changed 9 years ago by arma

Owner: set to runa
Status: newassigned

comment:2 Changed 8 years ago by runa

That is a good question. The projects are listed alphabetically, with bridgedb first and the website last. It is not possible to create sub-projects, and removing and adding projects in reverse order will not make any difference.

What kind of ordering would you like to have? We can always put in a feature request ticket.

comment:3 in reply to:  2 Changed 8 years ago by arma

Replying to runa:

What kind of ordering would you like to have? We can always put in a feature request ticket.

I'd like to order them by priority. That is, whichever files we most what translated. For example, we would put the core Vidalia files, the core Torbutton files, and the high-priority website files at the top of the list.

Do you need help choosing priorities for an ordering? I had figured it was mostly a technical issue on the transifex side (that it's hard to specify priorities), rather than that we don't have a plan on our side.

comment:4 in reply to:  2 Changed 8 years ago by arma

Replying to runa:

The projects are listed alphabetically, with bridgedb first and the website last.

Ah ha. That means we can hack around it on our side, if we want to. For example, we could put numbers at the beginning of each file name, like we already did with the website files (well, tried to do, since the current list of website files clearly isn't doing what we wanted it to do).

comment:5 Changed 8 years ago by runa

Well, Transifex lists things alphabetically and I can put in a feature request ticket to allow project maintainers to choose the ordering themselves. In the mean time, we can rename the resources so that the core Vidalia files show up on top of the list, followed by the core Torbutton files etc.

I will need help choosing priorities for an ordering. Then I can rename the resources on the Transifex website (yep, with numbers, like you just mentioned).

comment:6 Changed 8 years ago by arma

Here's a first go at priorities:

--Highest priority--
website - 1-high.index.pot
vidalia - vidalia.pot
vidalia - qt.pot
torbutton - torbutton.dtd.pot
torbutton - torbutton.properties.pot
website - /download/3-low.download.pot
website - /docs/1-high.tor-doc-windows.pot

--High priority--
torcheck - TorCheck.pot
website - /about/2-medium.overview.pot
vidalia installer - vidalia.pot
vidalia help - bridges.pot
vidalia help - running.pot
vidalia help - troubleshooting.pot
BridgeDB - bridgedb.pot
gettor - gettor.pot
website - /docs/1-high.proxychain.pot
website - /docs/1-high.bridges.pot

--Medium priority--
orbot - strings.pot
torbutton-alpha - torbutton.dtd.pot
torbutton-alpha - torbutton.properties.pot
vidalia help - index.pot
vidalia help - links.pot
vidalia help - log.pot
vidalia help - netview.pot
vidalia help - server.pot
vidalia help - services.pot
vidalia help - config.pot
website - /projects/1-high.torbrowser.pot
website - /projects/1-high.torbrowser-split.pot
website - /docs/2-medium.tor-doc-osx.pot
website - /docs/2-medium.installguide.pot
website - /docs/2-medium.documentation.pot
website - /docs/2-medium.verifying-signatures.pot

--Low priority--
website - /torbutton/3-low.torbutton-faq.pot
website - /about/2-medium.torusers.pot
website - /docs/3-low.android.pot
website - /docs/3-low.debian.pot
website - /docs/3-low.debian-vidalia.pot
website - /docs/3-low.rpms.pot
website - /docs/2-medium.tor-doc-relay.pot
website - /docs/2-medium.faq.pot
website - /docs/3-low.faq-abuse.pot
website - /docs/3-low.tor-hidden-service.pot
website - /download/3-low.download-unix.pot
website - /docs/3-low.tor-doc-unix.pot
website - /getinvolved/3-low.mirrors.pot
website - /docs/3-low.trademark-faq.pot
website - /getinvolved/3-low.tshirt.pot

--Optional--
website - /about/3-low.board.pot
website - /about/3-low.contact.pot
website - /about/3-low.contributors.pot
website - /about/3-low.corepeople.pot
website - /about/3-low.financials.pot
website - /about/4-optional.gsoc.pot
website - /about/3-low.sponsors.pot
website - /about/3-low.translators.pot
website - /about/3-low.volunteers.pot
website - /docs/3-low.N900.pot
website - /docs/4-optional.running-a-mirror.pot
website - /docs/3-low.hidden-services.pot
website - /docs/3-low.tor-doc-web.pot
website - /donate/3-low.become-sponsor.pot
website - /donate/3-low.donate-hardware.pot
website - /donate/3-low.donate.pot
website - /donate/3-low.donate-service.pot
website - /donate/3-low.matching-program.pot
website - /download/3-low.thankyou.pot
website - /getinvolved/4-optional.open-positions.pot
website - /getinvolved/4-optional.research.pot
website - /getinvolved/4-optional.translation-overview.pot
website - /getinvolved/4-optional.translation.pot
website - /getinvolved/4-optional.volunteer.pot
website - /press/4-optional.2008-12-19-roadmap-press-release.pot
website - /press/4-optional.2010-03-25-tor-store-press-release.pot
website - /press/3-low.inthemedia.pot
website - /press/3-low.press.pot
website - /projects/4-optional.arm.pot
website - /projects/3-low.gettor.pot
website - /projects/3-low.projects.pot
website - /projects/3-low.puppettor.pot
website - /projects/4-optional.torbrowser-details.pot
website - /projects/3-low.tordnsel.pot
website - /projects/3-low.torweather.pot
website - /projects/4-optional.vidalia.pot
website - /torbutton/3-low.index.pot
website - /torbutton/3-low.torbutton-options.pot

--Don't translate--
website - /docs/2-medium.manual.pot
manual pages - tor.1.pot
manual pages - tor-resolve.1.pot
manual pages - torify.1.pot
website - /download/1-high.download-easy.pot
vidalia-help-config-pot

comment:7 Changed 8 years ago by runa

Why shouldn't we translate manual.pot, download-easy.pot and config.pot? Granted, manual.pot only contains one string, but the two other files have lots of strings and are still in use.

comment:8 Changed 8 years ago by arma

It turns out download-easy is actually worth translating (#2842). I'd put it at 'high' priority for now, given the tension between a) nothing on the Tor website links to it and b) a few external blogs have been linking to it.

As for translating the manual.pot, I guess I don't mind. But didn't we decide not to build translated manuals on the website? In that case a translated page saying "here's the manual, only in English" will not help much at all.

As for "vidalia-help-config-pot", I believe it is identical to "vidalia help - config.pot" which is already in the list.

comment:9 Changed 8 years ago by runa

Resolution: fixed
Status: assignedclosed

I put download-easy at "high" priority, removed manual.pot and fixed "vidalia-help-config-pot" / "vidalia help - config.pot". All resources should now have a translation priority.

comment:10 Changed 3 years ago by isabela

Component: User Experience/TranslationsCommunity/Translations
Note: See TracTickets for help on using tickets.