Translating talk:Encyclopedia of Life
- [View source↑]
- [History↑]
Contents
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
Used in an administrator's interface to define new URIs associated with triplestore data. See http://en.wikipedia.org/wiki/Triplestore ... This term describes a relationship between two nodes in which the predicate allows a unit type specified by the object. This phrase will NOT be used in sentence form, it's a selectable 'type' of relationship between predicate and object.
Used in an administrator's interface to define new URIs associated with triplestore data. See http://en.wikipedia.org/wiki/Triplestore ... This term describes a relationship between two nodes in which the predicate is the inverse of the object. This phrase will NOT be used in sentence form, it's a selectable 'type' of relationship between predicate and object.
...Explanation added to qqq:
known_uri_label_allowed_unit: "Used in an administrator's interface to define new URIs associated with triplestore data. See http://en.wikipedia.org/wiki/Triplestore ... This term describes a relationship between two nodes in which the predicate allows a unit type specified by the object. This phrase will NOT be used in sentence form, it's a selectable 'type' of relationship between predicate and object."
Oops, correction; it's still there.
Used in an administrator's interface to define new URIs associated with triplestore data. See http://en.wikipedia.org/wiki/Triplestore ... This term describes a relationship between two nodes in which the predicate is the inverse of the object. This phrase will NOT be used in sentence form, it's a selectable 'type' of relationship between predicate and object.
Added to qqq.
As with all "activerecord.attributes.*" translations, these are translations used for creating forms and generating error messages and the string provided is meant to capture a particular field on a particular model.
However, in this case I suppose it's worth clarifying that a "triple" is a form of data storage, where you have a predicate, relationship, and object. So, for example, a single triple might be "American robins [predicate] prey on [relationship] worms [object]". In this case, we're talking about an "eol statistic", so we're counting the total number of triples in the database at a given point in time.
I've added that to the qqq.
I found message flag 'trusted' where is in reviewed media tags isn't translated(tag is <p class="flag trusted">Trusted</p>). Please fix it.
Thanks for pointing this out, but without more information, I'm not sure this is actually a problem. A quick "git grep Trusted app/views" doesn't show any results. It's entirely possible what you saw was caused by a missing database translation, but without knowing specifically where you saw it, it is hard to say.
Could you be more specific about where you saw this?
Thanks.
For example, trusted mark of media page http://eol.org/set_language?language=ko&return_to=http%3A%2F%2Feol.org%2Fpages%2F1049644%2Fmedia (Korean) is not translated as "신뢰할 수 있음". Tagalog and Serbian also aren't translated. It is may be at one of "Website-trusted", and "Database-translated activities-name-activity id-58"(message "unreviewed" is at "Database-translated activities-name-activity id-59").
p.s. In pages http://eol.org/data_objects/13164279, message "Database-translated agent roles-label-agent role id-9"(Photographer) isn't reflected. In Main Page (http://eol.org/) and statistics page of content partner (http://eol.org/content_partners/9/statistics) aren't translated messages for month and past time.
What does this "contact subject" actually mean? Is it a noun phrase or verb phrase?
In this case, this is a field on the "contact us" form. But...
Everything in the "Website-activerecord.attributes" subdomain is... tricky. It's a built-in Ruby on Rails convention, used for several different things. Most notably, it will be used to construct the form for whatever is being edited, so it will be used as the name for a field on a form. Secondarily, it will be used in automated error messages, such as "Contact subject is required".
I think you can *fairly* safely treat these as if they are noun phrases in the nominative case.
Red hot chili peppers? Meaning: please provide some context what this is.
None of the "Database" entries truly have a context, because they are pulled from the database (!) onto the pages as needed.
In this particular set (translated ranks), what you're translating is what biologists call a "rank," ie: Kingdom, Phylum, Order, Species, etc. This particular term (forma) is used by botanists, for example broccoli and cabbage are two different "forma" of a single species (believe it or not). Wikipedia says it well enough: http://en.wikipedia.org/wiki/Forma_(botany)
This is the sort of context needed. :) I've added it to EOL:Database-translated ranks-label-rank id-107/qqq; please do the same for other specific terms. If you also have particular indications (e.g. to keep in Latin, to follow scientifical terminology etc.), this is also useful context to add to qqq.
None of the "activerecord.attributes" values really have a context; this is a Rails-ism, used to construct field labels and error messages about those fields. For example, this string would be used to build the label "replace duplicates" to the checkbox on the form for collection_jobs.
...Since this same logic applies to ALL of the "activerecord.attributes" values, I don't feel inclined to include this in the qqq. But if you disagree, please let me know how you would like these to be handled.
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life
- Closed support requests for Encyclopedia of Life