2012-05-01: Support was added for Waymarked Trails. (Other news...)
Translating talk:Encyclopedia of Life
- [History↑]
Contents
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
Displaying %{start_number} — %{end_number} of %{total}
What does " —" mean? How to translate this?
Template:PLURAL How to translate this? What does {{PLURAL|one= mean? Actually, I find 94 cases of "{{PLURAL" on this page "http://translatewiki.net/w/i.php?title=Special%3ATranslate&taction=translate&group=out-eol-0-all&language=zh-hans&limit=5000&task=view".
See Plural.
In brief, PLURAL: expects a numerical argument, and uses the first branch for a value of one (or zero, I think), and the second branch for a value of two or above. It is used to adapt the text to the number case. For instance, a message could read "There is 1 user" or "There are 2 users" by being written "There {{PLURAL:$1|is|are}} $1 users".
The odd messages you found that read PLURAL|one=... don’t make sense to me. Maybe someone else knows better?
See also http://translatewiki.net/wiki/Plural
EOL uses the CLDR plural rules. Chinese (zh) has one form only in the CLDR database, the "other" form. Therefore the pattern for writing plural for EOL in Chinese (using the example of the above message) is {{PLURAL|translation of %{count} validation errors found}}. The software will display a number instead of "%(count)".
Patchwork message? Website-activerecord.attributes.open authentication.token ("Token")
Nope, those are just field names (these are used in validations), but thanks for checking.
Ah, I thought there may be a connection to Website-activerecord.attributes.open authentication.secret ("Secret") Cheers
Hi, I'm not sure about the translation unless I see the original sentence or place. So is it possible to find the original place of the word being translated?
ALL of the translations in the "EOL:Database" collection will be without context. All of them appear as potential values in a table (usually; sometimes as headings)... rarely if ever in sentences (since we know they don't translate well that way).
In the case of all of the "translated activies-name-activity" values, they are used to indicate the type of activity that was taken on either a data object (image/video/sound) or name during curation or editing. You happened to pick one of the lowest-priority sections of words to be translated, though. :)
More important (in order of my personal opinion of importance, loosely based on how frequently they appear on the site):
- translated_vetted-label-vetted
- translated_visibilities-label-visibility
- translated_data_types-label-data_type
- translated_licenses-description-license
- translated_ranks-label-rank (though many of these are hard if not impossible to translate, others are _very_ important)
- translated_table_of_contents-label-table_of_contents
- translated_agent_roles-label-agent_role
- translated_view_styles-name-view_style
- translated_sort_styles-name-sort_style
- translated_untrust_reasons-label-untrust_reason
- translated_contact_subjects-title-contact_subject
- translated_synonym_relations-label-synonym_relation
- translated_resource_statuses-label-resource_status
...The rest of the EOL:Database translations are really nice-to-have, not need-to-have.
Hope this helps!
Sorry, guys, but we've just pushed MAJOR MAJOR changes to the en.yml file. You should find several hundred new translations waiting.
...IMO, though, this is a HUGE improvement to how EOL handles activity logging.
We appreciate all the help!
It is cool to see that German translations rolled into EOL in the meantime. However, since there are still heaps of English language interface messages I suspect that not all of them have made it to the website by now. Is this observation correct? If yes I will wait a while until I start "debugging" my translations. If not it will be a terribly difficult to look which messages are missing from translation. Cheers
Nope. Just go to EOL and choose German as the interface language and see for yourself. It's an English/German mix with no apparent scheme. :(
Zum Beispiel, bitte?
I'm not finding much that's untranslated, with a quick spot-check. Sorry!
:) Yeah, something must have happend during the past three weeks since I posted this. This is much better. As a quick find I can at the moment only see something like "Vor about 7 hours" in the activity log. Now it is up to me to go through the page and optimise translations. I case I find something I will post it here. Cheers
I have realised that some messages get automatically transformed, like in Website-what_is_eol ("What is EOL?") all letters get captitalised. This is ok in all cases. What causes real big problems is, that all the messages on buttons get transformed into small letters like Website-helpers.submit.user.create ("Create account"). This is not possible since it is a major typo. Thus it is not ok in all cases. In cases like this the text transferred from translatewiki.net cannot be transformed at all. Cheers
Drat; I should have thought of that. :\
We'll have to talk about this one, since it's a lot of work to fix this. Sorry...
Yes. The automatic adjustment of case is good for quite a few languages, so we should not generally forbid it. Can we have a switch in the language configuration, which is usually "allowed" but can be "disabled"?
Unrelated: It may be useful to evaluate using his setting as well to set the installation default of: "allow lowercase page titles."
https://bugzilla.wikimedia.org/35260 is related too.
I'm in the process of replacing the #downcase calls in the code to #safe_downcase, where possible. I'm going to "whitelist" languages where downcasing is okay. ATM, this is just [:en, :es, :fr].
...If you're reading this and you know your language is safe, could you please reply here? :)
So:
>> "This is a Test".safe_downcase => "this is a test" >> I18n.locale = :es => :es >> "This is a Test".safe_downcase => "this is a test" >> I18n.locale = :de => :de >> "This is a Test".safe_downcase
=> "This is a Test"
Hi, this message talks about joining the team. I guess community is more appropriate to use in this message. Additionally all other messages related to this one are about community and not team. Cheers
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |



