View source for Thread:Support/About EOL:Website-known uri label inverse/en/reply
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.
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in the group: Users.
You can view and copy the source of this page.Jrice (talk)
...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?
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.
Okay, great, thanks. Now I know what went wrong.
I'll try and fix this later this week (it's a matter of running a script in production, which I don't want to do without testing.) :)
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.
Closing para tag should be in code, not in message. It is also unbalanced, as there is no open tag.
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.
Last edit: 11:53, 14 April 2013
The <p> tag seems to be unneeded in the translation. Move it to the code.
When working on the project "Encyclopedia of Life", should the name of the project be also translated into Czech ("Encyklopedie života") and its frequently used acronyme EOL substituted by its Czech equivalent EŽ? Or are they to be kept in their original form?
I think you can choose what you like here, as long as it's implemented consistently.
You can choose either, and the trick is to find the biggest community to reach an agreement on whether to translate. If the Czech community on Encyclopedia of Life is not very big, perhaps you could discuss on the Czech wikipedia, with links from the Portal:Cs. Do they have language community pages on EOL?
A related issue is whether to change the abbreviation EOL.
A quick review of the EOL home page shows that most, but not all, language verions have translated the name (in the header 'Currently in the Encyclopedia of Life' towards the bottom of the page). Most, but not all, have left the acronym EOL as it is. In all cases, the logo EOL with Encyclopedia of Life underneath it, stays in English.
No Czech community pages on OEL, no website on the Czech wikipedia yet. Well, this will surely change once the EOL communicates also in Czech language. Until then I will use the original EOL acronym.
I was just thinking that the EOL has its own website, whereas the Czech name points to nowhere, for some time at least. Could this be a problem?
Please provide a link to the "Czech name points to nowhere".
Links should not be localised. Instead they should be kept as they are. There is a drop-down box to switch the language at the top of the EOL site.
Are these localised links coming from messages? If so, please list them so that the documentation can be written to stop these links from being translated.