Except from image containing text, defining translations strings in quite easy.
How can I show it to you before submitting a patch?
The easiest thing would be to create a ticket and label it with
[RESEARCH] and [PATCH] in the title and attach your patch to that. Even
if you aren’t quite ready for your changes to be used by others, doing
it that way a great way to show us what you are up to.
By the way, why using images to display text?
It is the the easiest way to create buttons with rounded corners as I
designed them. If Radiant offers full multi-lingual support they will
definitely need to be replaced with simple text.
It is the the easiest way to create buttons with rounded corners as I
designed them. If Radiant offers full multi-lingual support they will
definitely need to be replaced with simple text.
For something like this why not just use the rounded image as a
background
and put the text on top of it?..straight CSS with no JS to muck around
with. Just a thought…
The only problem I see with doing text on static images is that, in
the long term, some translations may be quite a bit longer or shorter
than others. I guess the translation could include style attributes
to resize text when necessary.
The only problem I see with doing text on static images is that, in the
long term, some translations may be quite a bit longer or shorter than
others. I guess the translation could include style attributes to resize
text when necessary.
James
Ahh, but that’s why the good people over at ALA exist: to solve everyone
else’s problems! We could use a derivative of sliding doors 1 or
something
similar. JS or pure images or … whatever is fine because Radiant will
still rock no matter what, but personally I prefer straight up HTML+CSS
whenever possible.
The easiest thing would be to create a ticket and label it with
[RESEARCH] and [PATCH] in the title and attach your patch to that. Even
if you aren’t quite ready for your changes to be used by others, doing
it that way a great way to show us what you are up to.
Ahh, but that’s why the good people over at ALA exist: to solve everyone
else’s problems! We could use a derivative of sliding doors [1] or
something similar. JS or pure images or … whatever is fine because
Radiant will still rock no matter what, but personally I prefer straight
up HTML+CSS whenever possible.
I had to remove the vendor/plugin/gloc from the patch to reduce its
size. Also note that I had some trouble starting Radiant with GLoc,
apparently because of the frozen Rails. I couldn’t figure out why
because I’m running the exact same version on my computer.
Though as mentioned elsewhere, the sliding doors solution is also a good
one, though in a controlled environment like the admin console, rico’s
also a good solution.
I had to remove the vendor/plugin/gloc from the patch to reduce its
size. Also note that I had some trouble starting Radiant with GLoc,
apparently because of the frozen Rails. I couldn’t figure out why
because I’m running the exact same version on my computer.
Let me know about it.
Looks nice Fredric. A surprisingly small amount of modifications! Does
this automatically set the content type based off of the content type
the browser prefers? Or is the language set once globally?