|
|
|
Home » Community » U++ Webs: Functioning, Layout , Design, Features and Structure of these forums, homepage etc. » Index page translation
|
|
| Re: Index page translation [message #26466 is a reply to message #26463] |
Wed, 05 May 2010 13:31   |
|
|
Hi Koldo!
I'll take care about the Czech translation. I was planning to translate the website anyways... Even though Czech is not a world-wide language I think there is quite high ratio of Czechs in our community, especially between the core developers 
BTW: It would be nice if we could display the index page in users preferred language (as configured in the browser). Technical details: Browser sends HTTP_ACCEPT_LANGUAGE header, which contains an array of languages with their priorities. We should serve the best one available or use English as fallback. Unfortunately, it would require a little changes to uppweb. The easiest way to do it (AFAIK) would be a simple php wrapper (i.e. load index.php that would just choose the correct language and serve index$xx-yy.html). It could be probably done on the apache level as well, but I don't have the skills. It could be also done using javascript on client side, but that would be buggy and ugly.
Best regards,
Honza
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Index page translation [message #26476 is a reply to message #26473] |
Wed, 05 May 2010 23:18 |
|
|
I think for all-known project - yes you can remove the overview. But while community leaders and project schetayut that ULTIMATE still not known, it is better to leave these pages in the main index (this is my personal opinion which may not coincide with the majority opinion)
PS
We need more opinions to the discussion.
SergeyNikitin<U++>( linux, wine )
{
    under( Ubuntu || Debian || Raspbian );
}
|
|
|
|
| Re: Index page translation [message #26478 is a reply to message #26471] |
Thu, 06 May 2010 02:45 |
|
|
| andrei_natanael wrote on Wed, 05 May 2010 16:04 |
Hello
About index page, i think some links are redundant, they appear in both sections "Getting Started" and "Users". IMO Overview and Comparison should be removed from User section and remain only in Getting Started section because a user of U++ doesn't read overview and comparison every time but only first time when he start with U++.
|
I totally agree.
| andrei_natanael wrote on Wed, 05 May 2010 16:04 |
Also pages like Web index which are marked as "To be done" should not appear unless they exists.
|
As Koldo said, if it is not there, it will be never done I think that inactive link with this note is quite self-explaining, so nobody gets confused. And I also believe, that within three months, someone will implement this functionality 
Honza
|
|
|
|
|
|
| Re: Index page translation [message #26480 is a reply to message #26479] |
Thu, 06 May 2010 08:53 |
 |
koldo
Messages: 3432
Registered: August 2008
|
Senior Veteran |
|
|
| andrei_natanael wrote on Thu, 06 May 2010 08:43 |
| sergeynikitin wrote on Thu, 06 May 2010 00:18 |
I think for all-known project - yes you can remove the overview. But while community leaders and project schetayut that ULTIMATE still not known, it is better to leave these pages in the main index (this is my personal opinion which may not coincide with the majority opinion)
PS
We need more opinions to the discussion.
|
Sorry for confusion, i don't want to remove Overview from the main index but only duplicated links from it and Overview and Comparison appear twice. Please re-read my previous post.
Another concern i have is about page layout. If one change the layout of one page the change will not propagate to other pages (e.g. translated pages) because the layout is included with every page so Topic++ doesn't help too much here. What if we have one page (for every page) with text in english and a tool which will extract the text from it, put it on .t files. The translators will translate text from .t file and the tool will integrate the text back in page for every language, in case that the layout of the page has changed the change will be visible to all pages. It also help in case that there are some modifications to original text.
For example:
We have index$en-us.tpp. A tool will parse the file ignoring T++ tokens and extract all text in one file named index.t. The translators will do their job and at midnight when site get synced the tool will integrate translations in page so if we have in index.t file translations for Spanish and French the tool will generate index$es-es.html and index$fr-fr.html using the layout from index$en-us.tpp file so if any change appear to main index it will propagate to other translated indexes without the need of translator to modify by hand the layout of page.
Andrei
|
I agree, good idea... if we agree to maintain the basic page layout. In fact that technique is used in more places in uppweb , so it is easy to use it.
HEY!, two new languages have been added from yesterday:
- romanian thanks to andrei-catalin
- czech thanks to dolik.rce
... it is very easy
Best regards
Iñaki
|
|
|
|
| Re: Index page translation [message #26481 is a reply to message #26480] |
Thu, 06 May 2010 08:56 |
andrei_natanael
Messages: 262
Registered: January 2009
|
Experienced Member |
|
|
| koldo wrote on Thu, 06 May 2010 09:53 |
| andrei_natanael wrote on Thu, 06 May 2010 08:43 |
| sergeynikitin wrote on Thu, 06 May 2010 00:18 |
I think for all-known project - yes you can remove the overview. But while community leaders and project schetayut that ULTIMATE still not known, it is better to leave these pages in the main index (this is my personal opinion which may not coincide with the majority opinion)
PS
We need more opinions to the discussion.
|
Sorry for confusion, i don't want to remove Overview from the main index but only duplicated links from it and Overview and Comparison appear twice. Please re-read my previous post.
Another concern i have is about page layout. If one change the layout of one page the change will not propagate to other pages (e.g. translated pages) because the layout is included with every page so Topic++ doesn't help too much here. What if we have one page (for every page) with text in english and a tool which will extract the text from it, put it on .t files. The translators will translate text from .t file and the tool will integrate the text back in page for every language, in case that the layout of the page has changed the change will be visible to all pages. It also help in case that there are some modifications to original text.
For example:
We have index$en-us.tpp. A tool will parse the file ignoring T++ tokens and extract all text in one file named index.t. The translators will do their job and at midnight when site get synced the tool will integrate translations in page so if we have in index.t file translations for Spanish and French the tool will generate index$es-es.html and index$fr-fr.html using the layout from index$en-us.tpp file so if any change appear to main index it will propagate to other translated indexes without the need of translator to modify by hand the layout of page.
Andrei
|
I agree, good idea... if we agree to maintain the basic page layout. In fact that technique is used in more places in uppweb , so it is easy to use it.
HEY!, two new languages have been added from yesterday:
- romanian thanks to andrei-catalin
- czech thanks to dolik.rce
... it is very easy
|
About romanian translations, was me not Andrei Cătălin
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Index page translation [message #26490 is a reply to message #26479] |
Thu, 06 May 2010 14:07 |
|
|
| andrei_natanael wrote on Thu, 06 May 2010 08:43 |
Another concern i have is about page layout. If one change the layout of one page the change will not propagate to other pages (e.g. translated pages) because the layout is included with every page so Topic++ doesn't help too much here. What if we have one page (for every page) with text in english and a tool which will extract the text from it, put it on .t files. The translators will translate text from .t file and the tool will integrate the text back in page for every language, in case that the layout of the page has changed the change will be visible to all pages. It also help in case that there are some modifications to original text.
For example:
We have index$en-us.tpp. A tool will parse the file ignoring T++ tokens and extract all text in one file named index.t. The translators will do their job and at midnight when site get synced the tool will integrate translations in page so if we have in index.t file translations for Spanish and French the tool will generate index$es-es.html and index$fr-fr.html using the layout from index$en-us.tpp file so if any change appear to main index it will propagate to other translated indexes without the need of translator to modify by hand the layout of page.
Andrei
|
Hi,
I agree that having single layout would be very helpful. But I'm not sure if translating it with .t files is the best option as it would force translators to switch often between the .tpp and .t to see the context and that would be not very comfortable.
Better approach IMHO would be to change the T++ system a bit. The main idea would be having a single .tpp file for each topic and a DropList, to select which language should be displayed/edited. I believe that this would also help in most other situations. In 99% of cases, the documentation for each language is almost identical, with same layout, so even regular users would benefit from this solution. The underlaying implementation could be .t file and some QTF equivalent of t_ macro in .tpp that would be evaluated when interpreting the QTF. This solution would be a bit more difficult to implement and would have impact on whole U++, not just uppweb. Also care about backward compatibility would have to be taken.
What do you think?
Honza
|
|
|
|
| Re: Index page translation [message #26497 is a reply to message #26490] |
Thu, 06 May 2010 16:41 |
|
koldo
Messages: 3432
Registered: August 2008
|
Senior Veteran |
|
|
Hello Honza - Andrei
Perhaps this would have to be in another post, but think about this:
U++ lets application internationalization of strings using t_("") macros (and other things ).
However QTF has text messages inside, but it does not let direct internationalization. Indirectly you can, doing like this:
String txt = String("[2 ") + Format(t_("Last edit by %s on %s"), user, date) + ".]"
manually separating text from qtf format.
This can be done in code, but not in T++.
Two proposals:
1. To have an internationalized qtf, so that qtf strings under certain macro could be parsed, strings automatically got and put in some kind of .t file
2. T++ files could be automatically considered as international, so that .tpp file could have the layout and other file could have the translated messages.
3. Perhaps 1. .t files and 2. translated messages file could have the same format
4. These would match with Honza proposal too.
¿?
Best regards
Iñaki
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Sat Apr 26 19:33:28 CEST 2025
Total time taken to generate the page: 0.02761 seconds
|
|
|
Members
Pages
Help
Register
Login
Home
