View source for Thread:Translating talk:Encyclopedia of Life/About EOL:Website-term.name.by uri.http://purl(dot)obolibrary(dot)org/obo/RO 0002626/fr

I suppose “Nyakusa” is a misspelling of Nyakyusa language. Am I right?

Also, all these language names haven’t any doc. In what context are they displayed? In French, if they are include inside a sentence, the initial capital letter should be lowercased.

There is a typo in this message. Message is {user} changed created the collection but it should be %{user} created the collection

On it; thanks for reporting!

help or advice, please!

The ar.yml file is missing required pluralization cases throughout. It includes one/other cases, like in en.yml, but apparently requires additional cases, such as ‘many’, and perhaps others as well. See http://cldr.unicode.org/index/cldr-spec/plural-rules for an explanation. Example rails error: translation data {:one=>"تحتوي موسوعة الحياة على بيانات عن <a href=\"%{data_path}\"> سمة واحدة</a>:", :other=>"تحتوي موسوعة الحياة على بيانات عن <a href=\"%{data_path}\">%{count} سمات</a>، بما فيها:"} can not be used with :count => 55. key 'many' is missing.

Similar issue for fr: The key classifications.children.header_html is missing the ‘other’ pluralization case. The one case also looks incorrect. Rails error: "translation data {:one=>"</a> :"} can not be used with :count => 24. key 'other' is missing."

There is a typo in message: Image should be Video.

Thanks for reporting! That fix is committed.

Jen here, for the EOL team. We'd like to remove some messages from our corpus that are meant primarily for back end use and can be confusing to translate. Is there a good way to mark a set of keys (or all children of a given key) as not needing translation?

What is dir attribute? Direction / Directory attribute? (Hindi translation is using word "directory" (डायरेक्ट्री))

dir attribute means direction attribute

I think we should end support of this old version of EOL and start support the new one, because it's not very reasonable to translate it if it's not in use

Old version

New version which is currently in use

Absolutely agreed. It's a mess when I try to use it now. Do tell the main admins. I'll be glad to help. Cheers.

Hello! Jen here, from the EOL team. Is there any way we can help with this transition? We're preparing the codebase to internationalize the new platform, but we're not sure whom to alert about the relevant .yml files.

My developers tell me: "the .yml files are now in config/locales instead of config/translations."

Thanks!

Thanks, let us know which repository It's ok to tell here or file a request but you can also send a patch.

Thanks! The repository is https://github.com/EOL/eol_website.

This task has been documented at https://phabricator.wikimedia.org/T227102

OPEN This issue is open, waiting for action

This does not make sense. There are two instances of "in/on the pages API". Something is wrong with these phrases and needs to be rectified. I want to but I need context and description. Can someone more familiar to these correct them. Thanks.

OPEN This issue is open, waiting for action

Don't yell at users. "Warning" is enough.

OPEN This issue is open, waiting for action

We need an editor of variations between male and female.

OPEN This issue is open, waiting for action

Space missing after colon?

OPEN This issue is open, waiting for action

Space missing after colon?

OPEN This issue is open, waiting for action

Currently reads "EOL user %{user_full_name} requested a harvest requested for resource %{resource_title} belonging to content partner %{partner_full_name}". The "requested a harvest requested for resource" bit makes no sense. EOL:Website-notifier.content partner resource harvest requested request.message has a very similar problem.

CLOSED This issue is closed by Siebrand

typo: atricle -> article

Thanks. Fixed.

OPEN This issue is open, waiting for action

Is that colon right?

OPEN This issue is open, waiting for action

This message needs documentation.

OPEN This issue is open, waiting for action by jrice

• Its not about translation.

As a reader or user of thiis site, I hope two more functions to the EOL search.

1,Retaining the target word on searching box on the result page

 Sometimes, people like me make typo or add more key words to re-try the search.  
 It will help users who are not so good at the languages currently available.

2,Highlight or turn into bold the target word in the article shown

 Actually, I encountered my target word at the third line from the end of the text.
 I think it will be helpful too:D

I'm releasing bottled message...

Thanks for the comment.

I agree that highlighting the word and preserving the word typed in would be useful features. Thanks for the suggestion.

...We'll be re-vamping search in a few months, I'll keep these in mind when we get there.

OPEN This issue is open, waiting for action by Jrice

I know this site is displayed date like "January 1 2013"(%{month} %{day}, %{year}). In Korean, date is showed like "2013년 1월 1일"(%{year}년 %{month} %{day}일). In Chinese and Japanese, date is showed like "2013年 1月 1日"(%{year}年 %{month} %{day}日). but site is use only "%{month} %{day}, %{year}".

Apologies, this is (surprisingly or not) outside the scope of EOL translations. We rely on Sven Fuch's Rails I18n ( https://github.com/svenfuchs/rails-i18n ) for date translations. If the format is incorrect, it would actually need to be fixed there. :\

Sorry.

Is rails-i18n now being used? I recall that in the early days, there was a customised version in EOL...

아라, if you're interested, I could guide you to contributing to the rails i18n framework (if you don't know already or are not able to find out by yourself -- it would be a new thing for me too :P).

You're actually right that we don't include the gem in our Gemfile, but we use it to "bootstrap" the translations, periodically.

That said, I'd like to stop doing that, and integrate it. The problem is that it seems to enforce "proper" pluralization in Russian and Arabic, so we'll either need to not include those (less desirable) or add "few" pluralizations based on the "other" translations that exist at the moment.

I've put a ticket to that effect into our queue, but I don't know if we'll get to it in the near-term.

THAT said, we can always "steal" from rails-i18n at any time it's convenient, without adopting the gem fully, so if inroads are made there, we'll gladly grab the data at that point in time.

Any status update, Jeremy?

It's still on the TODO list, sorry. We've had some ... shall we say... "team restructuring" that has made it difficult to prioritize this task. Sorry!