On Sat, Sep 6, 2014 at 6:38 PM, Andrea Pescetti <pesce...@apache.org> wrote:

> On 03/08/2014 Kay Schenk wrote:
>
>> http://ooo-site.staging.apache.org/projects/native-lang-new.html
>>
>
> I see work on this has stopped, but the page was rather OK and a good
> replacement for
> http://www.openoffice.org/projects/native-lang.html
>
>  Ok, back to these ideas above. In my mind --
>> maintained -> current, and current -> maintained so these are one in the
>> same from a logical standpoint despite nuances in definition.
>> In a similar fashion, outdated -> unmaintained -> help wanted.
>>
>
> "Help wanted" is much clearer to people who are casually scanning the page
> and who are, in most cases, not native English speakers. So I tried to
> implement that. Similarly, I changed "Distribution" into "OpenOffice
> availability" since I find it clearer for non-native speakers.
>
>  So why not just call it "unmaintained" and provide some further
>> explanation by what is meant by this versus a separate entry in the table.
>>
>
> I completed the table with the recommended workflow for updating a
> translation.
>
>  Mostly, I am just trying to keep the maintenance and general
>> understanding of this page simpler for everybody.
>>
>
> I think it's pretty good now. Any other fixes to do before we replace the
> old native-lang.html with this one?


After skimming the native-language status page, I found these issues:

(1) while the website is "maintained", and the software is "current",
people may think that their help isn't needed. Here are a few phrasings
that could improve this misconception:
"maintained; more volunteers are welcome", or
"maintained; a few volunteers", or
"maintained by 3 volunteers"
etc.
(2) In addition to the website and software columns, I suggest to add a
Help System column, which can really lag behind the software translation,
and isn't apparent in the current table.

Tal

Reply via email to