[haiku-doc] Re: User Guide: Choosing a language


Le 22 juil. 09 à 19:29, Humdinger a écrit :
I guess the actually available translations in those menus can be inserted when exporting the pages from the db to HTML? 
Yes, that could be done.
I think the easiest way to do this would be to add <!-- LANG_MENU --> in the source page, and have a function in the tool to replace this with the actual menu in each generated page. I think I will make something similar for the navigation links, since translating them is difficult with the current system.
Now another question arises: What do we do when not all pages of the user guide are yet translated? Do we just wait until all are? Or do we fall back to English if there isn't a {LANGUAGE} page?
Good question. If a page was not translated in some language, it could be possible to update all links in other pages pointing to this page so they point to the English version but this would be tricky. I'd better generate pages even if they are not translated, or create symlinks. 


We already have a related problem: What about images?
Right now, since there isn't any localization, every language- dependent image is under /en/images/ and therefore /{LANGUAGE}/ images/ for translated pages. Do we just copy all images into the {LANGUAGE} hierarchy? Feels a bit bloaty. Is it possible to have links to the /en/images/* instead and just replace those piece by piece once localized versions appear? Can SVN handle this?
I'm not sure if Subversion can handle symlinks, since it works on systems that don't support them (Windows for instance). Maybe it would be better to put back the images in a not language- dependant folder, and wait for the apps to be translated for putting them into the {LANG}/ folders :) 

Vincent

Other related posts: