• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Multiple Language Support
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multiple Language Support


  • Subject: Re: Multiple Language Support
  • From: Chuck Hill <email@hidden>
  • Date: Mon, 27 Feb 2006 13:07:14 -0800

Hi Erik,

On Feb 25, 2006, at 2:48 PM, Erik Gillespie wrote:

I'm trying to make a decision about which framework(s) to use for developing a new project. One feature I would like to have is support for multiple languages, which I know both WebObjects and Struts support. The difference is in Struts you can put translations of any text in a property file and the rest of the page layout remains the same. The only example of multilingual support I've seen in WebObjects was one where each language had its own page so if you wanted to move the location of a form element (for example) you would have to modify the page for every supported language.

I think that is an artifact of the support for Yellowbox applications (long time ago) and maybe JavaClient to some extent. Yellowbox anyway had (IIRC) less automatic layout than HTML does. So, to get a clear, good UI in any language a specific UI for each was sometimes required.


In Struts you simply change a single page.

Yes, the default WebObjects way is not a good fit for HTML pages. One advantage of it is that you can also use it to manage the properties file for each language and save yourself some effort.


My question is if there is a way in WebObjects to have a single page that is based on text objects read from a file/database so I would only have to modify a page once if I wanted to change the layout?


There is, but it is not included in the product. I really like the WireHose (http://www.wirehose.com) implementation. You just bind things (like the value of a WOString) to @localize.keyFromPropertyFile (or something like that) and the frameworks look up the key in the right language in the right file and return the localized String. I believe that Project Wonder has something similar.


Chuck

--
Coming in 2006 - an introduction to web applications using WebObjects and Xcode http://www.global-village.net/wointro


Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects




_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Multiple Language Support (From: "Erik Gillespie" <email@hidden>)

  • Prev by Date: Page in Framework not found
  • Next by Date: Framework Page issues :(
  • Previous by thread: Re: Multiple Language Support
  • Next by thread: URI for static html/image
  • Index(es):
    • Date
    • Thread