Page MenuHomePhabricator

Create a translatewiki translation project for Web2Cit
Closed, ResolvedPublic

Description

We will have multiple source code repositories under the same project name. This should be possible, as inferred from the "Repository configuration" section of translatewiki's Setup a new project documentation:

Place repositories under a subdirectory named after the project if multiple repositories might be added for the project

We would have 4 separate translation subprojects:

  • Web2Cit server home & results page
    • repo: w2c-server
    • These are internationalized already and configuring translation via translatewiki should be trivial.
  • JSON editor content
    • repo: w2c-core, via JSON schemas
    • JSON schemas provide most of the messages seen on the JSON editor (see below). This depends on having our JSON editor support internationalization. See T305904.
  • JSON editor interface
    • repo: w2c-server, for now
    • There isn't much to be translated here, since most strings are provided via the JSON schema files that are used to generate the editing forms (see above). Still, there is some room for translation. See T316951.
    • Note that for now this is part of the Web2Cit-Server repository, but it may be split onto a separate project in the future. See T306837. We should explain that this may happen when requesting that the translation project be created.
  • Web2Cit editor
    • repo: w2c-editor
    • The new editor is already internationalized, but the software is not ready yet.
    • Also, we will have to ask what to do with translations coming from other projects (item types and Citoid field names from Zotero, and language names).

Parts not needing translation via translatewiki:

  • Web2Cit monitor
    • As long as I recall, the only parts worth translation are the custom templates that would be used in the overview, log and results pages written by the bot. I understand these templates should be translated on-wiki (i.e., outside of the translatewiki project).
  • Web2cit user script/gadget
    • We tried to keep changes made to the visual editor's UI as subtle as possible, precisely to avoid having to provide translation (see for example T311317, where using a pencil icon instead of the word "edit" was proposed). I understand this may bring problems with accessibility and we should revise this in the future.

Will all messages from different repos be grouped together? Do I have to do something to differentiate them? Or is this done by translatewiki?

Can we create a project now and add a logo later?

Because gitlab.wikimedia.org is not listed in the "Access for delivering translation updates" section of https://translatewiki.net/wiki/Setup_of_a_new_project, we'll need to contact someone to grant the appropriate push access.

Event Timeline

This was requested to the translatewiki collaborators here: T317047

Note that for now [the JSON editor] is part of the Web2Cit-Server repository, but it may be split onto a separate project in the future. See T306837.

Noting that it may make sense to have this split onto a separate project (maybe not yet specific, just w2c-json-editor to begin with) before starting translation. It may be confusing to have two separate translation sub-projects (server and editor) within one repository, otherwise.

w2c-core, via JSON schemas

I wonder whether we should have a repository separate from the core to keep these schemas. Automatic generation of schemas based on TypeScript types (T308347) should be taken into account for this decision.

I wonder whether we should have a repository separate from the core to keep these schemas.

See T318352.

diegodlh claimed this task.

Web2Cit project set up on translatewiki: https://translatewiki.net/wiki/Translating:Web2Cit