[wp-meta] [Making WordPress.org] #4252: De-prioritize plugin changelog translation
Making WordPress.org
noreply at wordpress.org
Fri Mar 8 12:09:37 UTC 2019
#4252: De-prioritize plugin changelog translation
--------------------------------------+---------------------
Reporter: Nao | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Translate Site & Plugins | Resolution:
Keywords: |
--------------------------------------+---------------------
Comment (by dd32):
Replying to [comment:8 Luciano Croce]:
> @dd32 about the B proposal (separate change log into a sub-project) what
do you think?
>
> Could it be a possible change?
Possible yes, but it's not something that I'm jumping to support.
Changelog data may not be as important to those who can translate (and
therefore read multiple languages) but it certainly would be valuable to
those who can't (Or are not as fluent at) read English.
To me, a proposal to split changelogs into a separate project is almost a
request to cease translations of them entirely.
I'm aware that's not the intention here, but it certainly feels like it
is.
I do agree that keeping ten years of changelogs is useless though, and
translating those old logs is a waste of everyone's time.
From a technical perspective, anything is possible, but segregating it
into a new protect would add a fair bit of hidden extra logic and code,
it's not as simple as it may first appear.
I think I'd rather invest in better tooling, perhaps where the priority
tagging is more effective than it currently is, perhaps stats of
percentage of high priority strings are translated rather than focusing on
full projects, etc.
#1078 is something that could help greatly with translating the readmes,
but probably also increase the approval workload.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/4252#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list