Translating talk:Encyclopedia of Life

From translatewiki.net
Jump to navigation Jump to search
First page
First page
Last page
Last page

Only the original author of this text object may edit it.

This looks like a sloppy error message.

Siebrand00:32, 22 December 2011

Yeesh. Agreed; changed to "Only the original author of this text object may edit it."

Jrice (talk)17:37, 27 December 2011
 

Google Analytics active

It should be "Google Analytics".

Siebrand00:30, 22 December 2011

Agreed (I see what the programmer was thinking, but he was wrong); changed.

Jrice (talk)17:35, 27 December 2011
 

Google Analytics results

It should be "Google Analytics".

Siebrand00:30, 22 December 2011

Agreed (I see what the programmer was thinking, but he was wrong); changed.

Jrice (talk)17:34, 27 December 2011
 

Spelling error: YouTube

Siebrand14:08, 19 December 2011

Thanks, fixed.

Jrice (talk)17:33, 27 December 2011
 

Spelling error: YouTube

Siebrand14:08, 19 December 2011

Thanks, fixed.

Jrice (talk)17:33, 27 December 2011
 

Context needed.

Siebrand14:07, 19 December 2011

This is used for the submit button on several admin pages, including content uploads, hierarchies, and search logs as an imperative verb to indicate the admin is about to update information in the database.

In qqq, now.

Jrice (talk)17:33, 27 December 2011
 

Context needed.

Siebrand14:03, 19 December 2011

This is used as a submit button on the admin interface for uploading images and PDFs to EOL's content servers.


Added to qqq.

Jrice (talk)17:29, 27 December 2011
 

Context needed.

Siebrand14:05, 19 December 2011

I'm not sure this _should_ be translated. [frown] It's the name of http://vivisimo.com and this string is used creating the link to that site on our "Search the Web" interface.

Jrice (talk)17:26, 27 December 2011

I added this to the qqq anyway. I suppose it could be "translated" to various alphabets/abugidas. [shrug]

Jrice (talk)17:27, 27 December 2011
 
 

Context needed.

Siebrand14:03, 19 December 2011

Added:

"This is a page title used on an administrative page where the admin can see and edit content (images, PDFs, and the like) which have been uploaded to EOL's content servers."

Jrice (talk)17:24, 27 December 2011
 

Context needed.

Siebrand14:01, 19 December 2011

Added:

"This is a low-level heading used on multiple documentation pages for the EOL API. The request, in this context, is the URL that a user would use to call the method being documented. It's the first H3 used on this page, for example: http://eol.org/api/docs/provider_hierarchies"

Jrice (talk)17:21, 27 December 2011
 

Please provide context.

Siebrand14:00, 19 December 2011

This is a very simple page title which is, unfortunately, difficult to describe succinctly. This was the best I could do:

"This is the title for a documentation page describing the API for retrieving provider hierarchy information: the names and ids of the taxonomy ('tree of life') that each of our providers (content partners) must build in order to give us information specific to species within that tree."


...Which I've just added to qqq.

Jrice (talk)17:16, 27 December 2011
 

is only allowed for the latest harvest event and only if that event is not already published

This looks like a patchwork message that should probably be reworked to use parameters.

Siebrand17:58, 1 December 2011

Not the case, but thanks for the suggestion.

Jrice (talk)18:55, 15 December 2011

Can you then please add message documentation?

Siebrand01:39, 19 December 2011

Done:

"This error message will be displayed (after the name of the checkbox on the form) if an admin attempts to flag a harvest event for publishisng in one of the cases where it cannot be published (ie: it musn't already be published and there must not be a more recent model to be published)"

Jrice (talk)17:09, 27 December 2011
 
 
 

What is the PLURAL based on? Both forms are identical in the English version.

McDutchie10:44, 8 October 2011

That happens more often in English. However, as you know, some translations do have different forms.

Siebrand10:04, 10 October 2011

Yes, I know. Once again, though, what is the PLURAL based on? I have no idea if and how I should pluralize in any other language if I don't know what it is that is being pluralized.

McDutchie18:01, 10 October 2011

It's a/the number (count).

Siebrand22:02, 18 October 2011

To expand, this is a message given in the context of an error. So, for example, this might imply that the value of "Age" is incorrect, because it must be over 18. so the message is presented to the right of the "Age" field and, in red, says "must be greater than 18".

So the plural is based on the minimum value. ...Which could, in theory, be one.


Hope that helps.

Jrice (talk)19:47, 15 December 2011

Thanks, that does help. It means that many of the existing translations of this message (that I can understand) are wrong. They pluralize the verb "must" based on the value of %{count}, but since the subject of the sentence is the field "Age", the verb should always be singular. I will fix the ones I can.

As far as I can tell, the PLURAL template would only be useful in this message if the translation includes the word (year(s)), for example, "(the age) must be greater than 18 year/years".

McDutchie (talk)19:10, 16 December 2011
 
 
 
 
 

Project still active?

It appears that the last time somebody answered here was end of October. Is there any information available?

[[kgh]] (talk)12:35, 13 December 2011

Sorry for the delay.  :\

Jrice (talk)19:21, 15 December 2011

Thank you for going through open issues. I hope to see you here frequently.

Nike (talk)12:53, 16 December 2011
 
 

Context needed. Probably part of patchwork message.

Siebrand18:01, 29 November 2011

Yes, kind of, but due to its complexity, it cannot be joined together.

I've actually changed the name of this key to make it slightly clearer what's going on (and because "to" is an AWFUL name, argh) and added this description:

"The value of this key is simply 'to' because it is used in the context of a date range, where the user inputs a start date before this string and an end date after it. ie: '...a user who registered from ____ to ____'"

Jrice (talk)19:34, 15 December 2011

I do not know about EOL, but in MediaWiki you could do this with placeholders that software replaces with input fields when the message is output. For Example:

Please specify: the event runs from $1 to $2 o'clock.
Purodha Blissenbach (talk)11:31, 16 December 2011
 
 

Hi, phone (202) 633-8730 is reachable in which country? What would I have to dial from, e.g. Germany? Whilst looking for some information on the EOL site I failed to determine the postal address of EOL. I strongly suggest to add this somehow too, not specifically to this message, but to the site as such. Cheers

[[kgh]]07:40, 9 October 2011

That looks like a USA/Canada phone number. These countries share the country code 1. From Germany you dial 00-1 first.

McDutchie10:42, 9 October 2011
 

I agree; I've added a little more information here. Thanks for pointing it out. (Personally I think it's silly that the number is hard-coded, but hey.)

Jrice (talk)19:51, 15 December 2011
 

What does IUCN stand for?

Pwyll11:13, 9 October 2011

It stands for this I will add a /qqq Cheers

[[kgh]]19:26, 9 October 2011

This should no longer be an issue; those keys with values including IUCN have the full name spelled out in one for or another (and this specific key is no longer in use).

Jrice (talk)19:49, 15 December 2011
 
 

Hi, there should be a full stop after "menu item" since "This" starts a new sentence. Cheers

[[kgh]] (talk)17:50, 20 October 2011

Yes. Changed. Thanks.

Jrice (talk)19:45, 15 December 2011
 

What are the possible values of %{type}? French call for a gender distinction (eg, "article" would be 'male' & "image" would be 'female').

Jean-Fred17:49, 5 June 2011

And not only gender matters, in fact, orthograph counts as well becaus ef euphonics. Eg, you would write « cet article » and « ce sujet », because the first one starts with a vowel.

Jean-Fred17:53, 5 June 2011
 

Understood. (For the record, the possible values are text, image, video, and sound.) This is a tough one; the EOL team is discussing it internally, but we appreciate the problem. Thanks for pointing it out.

In the meantime, is it possible to "avoid the issue" with something akin to "%{username} marked this object (%type) as inappropriate."  ?

Thanks again.

Jrice15:51, 6 June 2011

If the number of possibilities is limited, duplication is the best option. Just create 4 messages with one parameter less, instead of 1 with an additional parameter.

Siebrand12:22, 7 June 2011
 

I used the workaound you suggested. What about the solution Siebrand suggested?

Jean-Fred (talk)22:12, 29 October 2011

We've implemented other keys in this manner (since this particular key has since been removed).

Jrice (talk)19:43, 15 December 2011
 
 
 

What does this mean, "Comments on something" or "Comments feature turned on"?

Anakmalaysia (talk)06:09, 14 December 2011

This is meant to be the header for a page where we're listing all of the comments on a particular subject, such as 'Comments on An Image of A Blackbird' or 'Comments on Procyon Lotor' or 'Comments on Jeremy Rice'. Thus, this string is prepended to the title of the page where the comments were originally left, and these titles are supplied by content partners, so we CANNOT know the number, gender, or other information about the string.


I've added this information to the ancillary information for this key.

Jrice (talk)19:42, 15 December 2011
 
First page
First page
Last page
Last page