How to remove the link text "Share to>" from buttons?

[pablosalgadom]

Hello everyone,

I'm using this gem but when the icons link to share have a text "Share to>" and i don't know to remove, i've tryed removing line "share_to: Share to %{name}" from the "social_share_button.en.yml" but nothing happens.

I also look into the javascript file, but it isn't there, can someone help me on this?

Thank you!

[huacnlee]

There looks like not have I18n file

You need:

rails generate social_share_button:install

[pablosalgadom]

Thanks for your prompt answer huacnlee but what your are saying doesn't make sense, because i've done that, i've done every step in the read me of the gem and i still have the social button with the text "share to>" at the end of it. Would you pleaase help me on that? how can i remove it?

thanks, and i don't know why this it's closed when that wasn't the solution =/

[pablosalgadom]

in the demo page you have the buttons without the "share to>" text, but i don't know how to remove it :(

[huacnlee]

What is you Rails locale config

application.rb

config.i18n.default_locale = "en"

social-share-button just only have 3 I18n files: zh-CN, en, zh-TW.

[pablosalgadom]

Thank you!!! that was the proper solution to my problem!!

I was using an "es" language, that's why i was having a wrong behavior, the only thing that i have to do is create a file named like this example with this content and everything works great:

social_share_button.es.yml

es:
social_share_button:
share_to: Compartir en %{name}
weibo: Sina Weibo
twitter: Twitter
facebook: Facebook
douban: Douban
qq: Qzone
tqq: Tqq
delicious: Delicious
baidu: Baidu.com
kaixin001: Kaixin001.com
renren: Renren.com
google_plus: Google+
google_bookmark: Google Bookmark
tumblr: Tumblr
plurk: Plurk
pinterest: Pinterest
email: Email

IMHO i think that this could be in the readme for the ones that creates pages in other languages.

Many thanks :D

[albertopeam]

Thank you to @pablosalgadom to provide the trick, i also use 'es' and i had the same problem. I think that @huacnlee could add this to the readme to help the users of the gem.