On Feb 10, 12:11 pm, Hugo Palma wrote:
> I'm not sure i understand your solution, so your build process find an
> index.html and replaces all the text there to all the languages and creates
> the appropriate index_.html file ?
Yes
May seem like a hack, but on the other hand I honestly don't
un
On Wed, Feb 10, 2010 at 17:28, David Pollak
wrote:
> I think this idea is weak.
>
> Lift supports localized pages (e.g., index_en_US.html, index_it.html,
> etc.) Any page-level localization can be accomplished by writing a
> localized page. Any snippet-level localization can be achieved by passi
I'm not sure i understand your solution, so your build process find an
index.html and replaces all the text there to all the languages and creates
the appropriate index_.html file ?
If so, where do you keep the translated text at dev time ? Is it still on
resource bundles ?
On Wed, Feb 10, 2010 at
On Feb 8, 5:07 pm, Timothy Perrett wrote:
> Generally I find that to be only of use when needed specific adjustments to
> templates. For instance, english vs german... the german language is
> significantly more verbose so requires different div heights etc sometimes.
> Its not generally a stra
I think this idea is weak.
Lift supports localized pages (e.g., index_en_US.html, index_it.html, etc.)
Any page-level localization can be accomplished by writing a localized
page. Any snippet-level localization can be achieved by passing localized
XHTML as parameters to the snippet. Further, as
Interesting. What would an example where two pages in the same locale should
have different values for the same key used by the same snippet?
-
Hugo Palma wrote:
I think a simple inheritance concept would work just fine.
We could have:
application resource bu
I think a simple inheritance concept would work just fine.
We could have:
application resource bundle (what Lift has now) -> page resource bundle ->
snippet resource bundle
This would mean that every snippet would inherit the the resource bundle of
the page where it's being rendered. So yes, the
If the same snippet is used by two pages you would want two separate resource
bundles to be used for the same snippet?
-
Hugo Palma wrote:
So what you're saying is that a page can include a bunch of snippets and
that's why it doesn't be an advantage to have pa
mm im not sure who would take this on, as I think i've been doing most of the
localisation stuff and I don't have capacity to do anything about this for
quite some time unless it becomes an urgent priority.
Any discussion must take place on this list, not on (or in) tickets, review
board or ot
I understand, just trying to share some of my own experience and ideas.
So, should i create an issue for further discussion or do we just let it be
?
On Tue, Feb 9, 2010 at 18:43, Timothy Perrett wrote:
> Appreciate where you are coming from, however, the defaults are working
> quite well so perh
Appreciate where you are coming from, however, the defaults are working quite
well so perhaps it would be frugal to break some other boxed configurations
into lift-localization or something... Such as page related resource bundles.
Needs some thinking, but its certainly possible. Lift is extreme
So what you're saying is that a page can include a bunch of snippets and
that's why it doesn't be an advantage to have page resource bundles ?
I'm sorry but i don't see why.
I'm not sure how people are using resource bundles with Lift now but the way
i would do it would be to create a resource bun
Come to think of it - if you really wanted to have a resource bundle
for each page... you could do that using the resource bundle factories
I listed earlier.
Cheers, Tim
On Feb 9, 5:38 pm, Timothy Perrett wrote:
> The analogy would be MVC controllers... the index method has an index
> page and a
The analogy would be MVC controllers... the index method has an index
page and an index resource bundle. Within Lift, we dont use
controllers, so there is nothing stopping you calling a whole bunch of
snippets on a single page - thus, there would be no single "page"
resource bundle (that is, it wou
Some of the code needs adjusting because of an API change since I
wrote this, but this should give you a good overview of lifts
localization and templating:
http://is.gd/81uAi
Cheers, Tim
On Feb 9, 5:29 pm, James Matlik wrote:
> I would also be very interested in more detail on this topic. I've
I would also be very interested in more detail on this topic. I've been
toying with designs with a variety of technologies (a self-driven academic
activity this far) to formulate how a massively multilingual site (upwards
of 12 languages) could be implemented. I've not had much luck understanding
t
Sorry Tim but i don't quite understand what you mean by "page is
scoped to a single snippet" and that invalidates that you have a
resource bundle per page. Sorry is this is clear to everyone else but
i'm new with Lift so i'm still grasping basic concepts.
On Feb 8, 10:49 pm, Timothy Perrett wrote
17 matches
Mail list logo