Changes between Initial Version and Version 1 of Ticket #428


Ignore:
Timestamp:
Oct 3, 2007, 7:06:51 PM (17 years ago)
Author:
Nicolas
Comment:

I have reformatted your list to have numbered items, it's easier to refer to them that way.

I thought 1. had already been taken care of.

About 5., make sure any change to naming only affects end users. Documentation for project admins should still use the existing terms. Confusing or not, it's important to differentiate the workunit from the replication instance.

Coordinate with translators! Making the English words less confusing for new users will only help a fraction of the users: English-speaking ones.

I get confused on the Spanish translation when it says "Equipo". It means "team", but can also be one of the many ways to call a computer. What BOINC project websites use for "computer" is "ordenador" (like on top_hosts.php), which is actually only used in Spain. I think that word isn't used in any country from Latin America.

(Going a bit off-topic) Don't try to argue with Spanish people about it, it's much worse than arguing with somebody from England about color/colour ("we invented the language so our version is right", etc). There's more differences between Spain and Latin America Spanish than between UK and US English, so I don't understand why they aren't separated.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #428 – Description

    initial v1  
    11I wonder whether for boinc v.6 it might be possible to make certain elements of boinc vocabulary more accessible to the general public, and in one case standardize the current nomenclature.
    22
    3 * When a file upload fails, the phrase 'No space left on device' which appears in boinc manager messages always causes consternation on forums when some crunchers think their own disk is full. This is not fair to newbies. Could it be changed to 'The server (disk) is full' or 'No space left on server'?
    4 
    5 * I don't think many newbies can understand the BM message 'Scheduler RPC succeeded'. What about 'Boinc has contacted the (project) server'?
    6 
    7 * I think the BM message ' Access to reference site succeeded' is unnecessarily obscure. What about 'Boinc is able to contact other internet sites / a test internet site'?
    8 
    9 * Again for the benefit of newbies, would it be possible to change the word 'host' to 'computer' as a general rule? (When I first crunched I thought I was the host(ess) because I'd invited boinc and the project onto my computer.)
    10 
    11 * The last item is a biggie. At the moment the word 'workunit' is used for the basic task package of which several copies/iterations may be made   to be downloaded for crunching. I'm perfectly happy with this use of 'workunit'.
     3 1. When a file upload fails, the phrase 'No space left on device' which appears in boinc manager messages always causes consternation on forums when some crunchers think their own disk is full. This is not fair to newbies. Could it be changed to 'The server (disk) is full' or 'No space left on server'?
     4 1. I don't think many newbies can understand the BM message 'Scheduler RPC succeeded'. What about 'Boinc has contacted the (project) server'?
     5 1. I think the BM message ' Access to reference site succeeded' is unnecessarily obscure. What about 'Boinc is able to contact other internet sites / a test internet site'?
     6 1. Again for the benefit of newbies, would it be possible to change the word 'host' to 'computer' as a general rule? (When I first crunched I thought I was the host(ess) because I'd invited boinc and the project onto my computer.)
     7 1. The last item is a biggie. At the moment the word 'workunit' is used for the basic task package of which several copies/iterations may be made to be downloaded for crunching. I'm perfectly happy with this use of 'workunit'.
    128
    139I'm unhappy, however, about using the word 'result' to designate the workunit copies destined for crunching. 'Result' in ordinary language always implies consequences, yet boinc uses the word even for workunit copies that may never be sent out or crunched and  for which there will never be consequences.