We need to find the best way to add a BTN or link to: https://crowdin.com/project/joomla-official-sites
a kind of "Help us translate this site"
Ideas?
I have no specific opinion on this matter.
At least we have here 3 options.
The only thing I'm sure is: do NOT mention me this
I like @brianteeman's idea.
In this case, we would have a dedicated link per site OR a global one https://crowdin.com/projects/Joomla that would promote t9n also for Core & other ressources.
@Sandra97's translate btn (NOT in the etc. menu) would be maybe more efficient?
The only places we've really mentioned translations in the past were in the documentation, i.e. here and here. Those obviously need updates too.
As for where to put something site specific, I'd go for the menu bar. Probably the /etc
menu versus a top level button. Or maybe add something at the bottom of the language selector. I dunno, I just write PHP code, don't make me make design decisions!
Option 1 was my first idea but I have never been a fan of Icons instead of text. Even in this case, please let's use 2016 "Flat" monochrome instead of 90s' ones (one day, we will have to talk about the flags
something more like?
I also like the footer idea with: "Translate this site" if it is correct
I am really not a fan of an icon on the main menu navigation. That really
makes translating to be a major feature when in reality it's a request for
help that will only ever be relevant to a small number of people.
Especially now you already have so many languages available
Agree even if finding a way calling for translators is not an exclusive JIssue tracker "feature".
Some are coming on the Doc and are more confortable to translate Marketing stuff or others just want to help in core strings. My "job" is then to "catch" translators where ever they are, then work with them to find a place they will stay and be active a max of time.
At least for Joomla as a whole we could link to Crowdin in that often
forgotten globe menu on the top nav. Doesn't do much for the few sites
which are language aware (3.x landing page, help screens by way of the
wiki, tracker) but it at least adds something. Might be the worst starting
step ever but it is at least one.
On Monday, July 11, 2016, Marc-Antoine Thevenet notifications@github.com
wrote:
Agree even if finding a way calling for translators is not an exclusive
JIssue tracker "feature".
Some are coming on the Doc and are more confortable to translate Marketing
stuff or others just want to help in core strings. My job is then to
"catch" translators, then work with them to find a place they will stay and
be active a max of time.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#824 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAWfoUneHsz0gwJztj2CEtS7syJiiA3Gks5qUsCugaJpZM4JI0g5
.
the what?
The only thing I'm sure is: do NOT mention me this
? menu absurdity
https://www.youtube.com/watch?v=afMsXWRWbOk
At least I'm trying here. Never said the idea was good, but there's two things going on here:
1) Finding a way to encourage app/site specific translations
2) Trying to make project wide T9N more prominent
@MATsxm The icon looks excellent. I'd put it in right away if we all agree. (If you could find time to do it, that would be cool - I dont think that its a good idea to let @elkuku touch anything design related - he prefers PHP code
Te me it makes sense to put it right to the language selector, so the (small) group of people it is relevant to, will find it easily.
The footer link IMHO should be just an additional thing. Having it as the only option would mean next to nothing. (@brianteeman)
So we could have a project wide footer link (2) and, for sites that are "language aware", an icon next to the, already existent, language selector (1).
-1
On 12 July 2016 at 17:09, Nikolai Plath notifications@github.com wrote:
@MATsxm https://github.com/MATsxm The icon looks excellent. I'd put it
in right away if we all agree. (If you could find time to do it, that would
be cool - I dont think that its a good idea to let @elkuku
https://github.com/elkuku touch anything design related - he prefers
PHP code? )
Te me it makes sense to put it right to the language selector, so the
(small) group of people it is relevant to, will find it easily.The footer link IMHO should be just an additional thing. Having it as the
only option would mean next to nothing. (@brianteeman
https://github.com/brianteeman)So we could have a project wide footer link (2) and, for sites that are
"language aware", an icon next to the, already existent, language selector
(1).—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#824 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ABPH8UYQxo2enY1xg1peCrD1u_Sw0JxPks5qU7xGgaJpZM4JI0g5
.
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
@elkuku Thanks for the precious help.
I have few things to do right now (I heard there's a 3.6 around
Note that everything would be easier to fix if this joke of
As for where to put something site specific, I'd go for the menu bar. Probably the /etc menu versus a top level button.
+1
I would vote for /etc
Labels |
Added:
enhancement
UI
|
Still have few things to check but meanwhile and if needed, there's also this one that is more and more used as t9n icon.
http://fontawesome.io/icon/language/
We reach an action point here?
before having a global i18n solution, I would
"Help in translation" ?
Moved to website repo. At this point I think we need to go for a global solution over a site specific one (not to mention we already link to Crowdin in a couple places).
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-09-15 22:34:15 |
Closed_By | ⇒ | mbabker |
At spare time, I will make a proposal for the footer menu.
thanks
In the footer next to the report an issue link?