Main place for discussions about U++ cross platform development framework.
Ultimate++ Homepage Translations (RU...)
Re: Ultimate++ Homepage Translations (RU...)
Another question, how realistic do on site www.ultimatepp.org Russian menu on the left, if the person switched to the Russian language in the articles?
if Overview translated, I'll translate "Examples"...
Hmm, uppbox generates examples-page using the packages, so I can't change examples' info (any thoughts how to deal with that?). Well, I've translated what I can (including HelloWorld example). Best regards and sorry for my English. Anton.
Quote: Hmm, uppbox generates examples-page using the packages, so I can't change examples' info (any thoughts how to deal with that?). Well, I've translated what I can (including HelloWorld example). Hello Sc0rch The subject is not to translate pages, it is to insert new pages that are translations of older and are linked to them and to main web hyperlink web in a nice way. One example is in new Bazaar page. Read the documentation and tell me what do you think. Best regards Koldo
koldo wrote on Tue, 26 January 2010 03:56 The subject is not to translate pages, it is to insert new pages that are translations of older and are linked to them and to main web hyperlink web in a nice way. Hello Koldo, As I'm doing now, =) This evening, I'll try upload ru-pages to SVN with help of someone. P.S. Just inserting translated pages, not overwriting. koldo wrote on Tue, 26 January 2010 03:56 One example is in new Bazaar page. Read the documentation and tell me what do you think. Sorry, I'm new here. I have no idea where Bazaar is new, and where it is old, =) What kind of documentation / example? Best regards, Anton
Hey A web page in Russian ! http://www.ultimatepp.org/www$uppweb$overview$ru-ru.html Do not you think that we may do it in more languages ? (Why not in your language) Perhaps not all the documentation, but at least the: - Index (home page) - Overview - Comparisons - Download and of course - Funding Best regards Koldo
I have tried to provide such a way that not only the Russian translation could be placed on the site. The work of translation is not fast. We work together with Anton (sc0rch). We will translate all the articles gradually. I hope the representatives of other languages is also willing to do the translation. I do not know how to other countries, but Russia's situation is that the lack of translation is a serious barrier to start using the tool.
sergeynikitin, -30 C in our lands, sunshine)) I read what you've changed in my translation. That's right, the changes are correct. Thank you! P.S. I've fixed one misprint, sending changes to you. Best regards, Anton.
To speed up translation maybe use http://translate.google.com/# and check translation and correct? sergeynikitin wrote on Thu, 28 January 2010 05:06 I have tried to provide such a way that not only the Russian translation could be placed on the site. The work of translation is not fast. We work together with Anton (sc0rch). We will translate all the articles gradually. I hope the representatives of other languages is also willing to do the translation. I do not know how to other countries, but Russia's situation is that the lack of translation is a serious barrier to start using the tool.
Hi Ion. Yes we did so. Just write the original texts are not in simple english. When just reading the documentation, it does not require the literal sense. And when the translation, I want to extinct as possible.
Problem!! We've started to translate descriptions of some examples and discovered, that links in .tpp extract to html not correctly (for example see AnimatedHello links [en][ru])
sergeynikitin wrote on Sat, 06 February 2010 04:13 Problem!! We've started to translate descriptions of some examples and discovered, that links in .tpp extract to html not correctly (for example see AnimatedHello links [en][ru]) Hello Sergey Do you remember I told in other post that uppweb has "en-us" hardcoded everywhere ?. Well, this is one place. In addition uppweb does not try to take hyperlinks from Examples pages, so the [en][ru] links are lost. If nobody can do it in one week I would internationalize a little bit uppweb .cpp code.
Yes, I already understood this. I also try to look elsewhere this can be corrected.
Hello everyone! Thanks for the answers! I think, it would be ideal if the user could click the "RU" at top of page, go to the main Russian page, save it to his bookmarks and forget about switching the language. Also, if the article is not translated yet, the English version of the article can be displayed. What do you think? Just my thoughts. Sorry, if something wrong. Best regards! Anton. P.S. I have translated Index-page, looking for another...
Sc0rch wrote on Thu, 11 February 2010 14:19 Hello everyone! Thanks for the answers! I think, it would be ideal if the user could click the "RU" at top of page, go to the main Russian page, save it to his bookmarks and forget about switching the language. Also, if the article is not translated yet, the English version of the article can be displayed. What do you think? Just my thoughts. Sorry, if something wrong. Best regards! Anton. P.S. I have translated Index-page, looking for another... Hello Sc0rch All of it seems more than reasonable
I've added Header on index.html page during localisation. Please test it. I thing, that with header is better. Please share your opinion.
Hello Sergey Uppweb package does not compile. It seems it is something wrong with changed en-us index page: c:\upp\uppbox\uppweb\www.tpp\index$en-us.tppi(3) : error C2466: cannot allocate an array of constant size 0 c:\upp\uppbox\uppweb\www.tpp\index$en-us.tppi(3) : error C2143: syntax error : missing '}' before '<<' c:\upp\uppbox\uppweb\www.tpp\index$en-us.tppi(3) : error C2143: syntax error : missing ';' before '<<' c:\upp\uppbox\uppweb\www.tpp\index$en-us.tppi(3) : error C2143: syntax error : missing ';' before '<<' C:\upp\uppbox\uppweb/www.tpp/all.i(71) : error C2065: 'topic' : undeclared identifier C:\upp\uppbox\uppweb/www.tpp/all.i(71) : error C2065: 'title' : undeclared identifier C:\upp\uppbox\uppweb/www.tpp/all.i(71) : error C2065: 'data' : undeclared identifier C:\upp\uppbox\uppweb/www.tpp/all.i(71) : error C2065: 'data' : undeclared identifier C:\upp\uppbox\uppweb/www.tpp/all.i(71) : error C2070: ''unknown-type'': illegal sizeof operand C:\upp\uppbox\uppweb/www.tpp/all.i(71) : error C2065: 'data' : undeclared identifier C:\upp\uppbox\uppweb/www.tpp/all.i(73) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(77) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(81) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(85) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(89) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(93) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(97) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(101) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(105) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(109) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(113) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(117) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppbox\uppweb/www.tpp/all.i(121) : error C2447: '{' : missing function header (old-style formal list?) C:\upp\uppsrc\Core/topic_group.h(123) : error C2059: syntax error : '}' C:\upp\uppsrc\Core/topic_group.h(123) : error C2143: syntax error : missing ';' before '}' C:\upp\uppsrc\Core/topic_group.h(123) : error C2059: syntax error : '}' C:\upp\uppsrc\Core/topic_group.h(120) : error C2065: 'TOPIC__01_fn' : undeclared identifier
oooops I've not touched uppweb. It's maybe wrong all.i. Open www.tpp and touch index$en-us. Maybe it help. I've just compiled on my computer. All compiled OK.
Hello Sergei Please check file index$en-us.tppi. To be sure I have: - Deleted uppweb and downloaded from svn - Checked the file in upp-mirror This is the beginning: TITLE("Ultimate++ is a C++ cross-platform rapid application development framework") COMPRESSED <<<<<<< .mine 120,156,172, This is the end: >>>>>>> .r2061 The symbols >>>>>>> and <<<<<<< are not part of the file and seem to be added by svn. If you delete them the package compiles and runs.
Hello all Quote: I've added Header on index.html page during localisation. Please test it. I thing, that with header is better. Please share your opinion. Just to show it to everybody this is a detail of the new look of index page that Sergey proposes: Now this is off-line. Tomorrow it will be visible in web.
Quote: The symbols >>>>>>> and <<<<<<< are not part of the file and seem to be added by svn. They are added by svn in case that there are merge conflicts.
Hi Koldo! If there are doubts about modifying the home page, it can be brought up for discussion, or, in the end, nothing prevents us tomorrow or next week to return to the previous version. My pros and cons: - I hope that we can change the functional uppweb so that text typed script for more than 24 points in the HTML output would fall as the tag , and then these titles help us very much in search engine optimization. - Is the repetition of key words typed with a different style. Certainly it seems to me quite right to alter design of the main page and include plenty of keywords to go there and remove it from the list of files to download, because, again, for search engine optimization, the main holder of the keywords the site is the home page. I'd like (for search engine optimization is extremely important) to be able to links and images to include the tag TITLE, which shows a balloon, but the text of the tips is several times more weight than plain text for search engines.
sergeynikitin wrote on Fri, 12 February 2010 10:30 I'd like (for search engine optimization is extremely important) Frankly, my opinion is that it is much hyped, so that consulting companies can sell more... Mirek
I thing that title is perhaps OK, but I would not repeat the first sentence there.. However, the index page is more than 3 years old now (I believe), maybe we rather should take this oportunity to make some overhaul of the text? I suggest putting some screenshot back (I have removed it by me SEO consultant advice.. and perhaps make the screen more active, like giving directions (at least something "I am newbie" link or similar). Suggestions welcome. Mirek
In fact, the rules of search engines are constantly changing, so it is possible that I have knowledge may well be old (I certainly hope that this is not true).
luzr wrote on Fri, 12 February 2010 22:14 Suggestions welcome. Hello, Mirek! I think, HelloWorld example link can be placed on the main page (for newbies and maybe for interest of others =)). Best regards, Anton
Sc0rch wrote on Fri, 12 February 2010 21:29 luzr wrote on Fri, 12 February 2010 22:14 Suggestions welcome. Hello, Mirek! I think, HelloWorld example link can be placed on the main page (for newbies and maybe for interest of others =)). Best regards, Anton Maybe TheIDE + window of Layout Designer and there (in it) design of window of HelloWorld?
Hello Sergey I do not want to be annoying but for now index$en-us.tppi follows being corrupted so web will not work. If you do not believe me check this: Quote: http://code.google.com/p/upp-mirror/source/browse/trunk/uppb ox/uppweb/www.tpp/index%24en-us.tppi Perhaps your local copy is Ok but not the copy in svn.
Ok, I'll re-upload tonight all these files.
In fact in local copy everything ok while compiling uppweb.
koldo wrote on Fri, 12 February 2010 15:35 Hello Sergey I do not want to be annoying but for now index$en-us.tppi follows being corrupted so web will not work. If you do not believe me check this: Quote: http://code.google.com/p/upp-mirror/source/browse/trunk/uppb ox/uppweb/www.tpp/index%24en-us.tppi Perhaps your local copy is Ok but not the copy in svn. Seems ok in svn... Anyway, for sergey: Please do UPDATE before doing any work to avoid conflicts. Mirek
Hello all Now Upp web is a little bit more international. Could you find something different ? Now uppweb has a .t file with supported languages. If you want to add a new one: - include the new language and the messages in .t - go to www.cpp and add your language here: languages.Add(LNG_('E','N','U','S')); languages.Add(LNG_('R','U','R','U'));
There is a small problem with the translation Funding Ultimate++. In Russia, limited use of PayPal (perhaps not only in Russia). Perhaps there are similar international instruments? In Russia (and in post soviet countries) very common WebMoney (http://www.webmoney.ru/ or english link http://www.wmtransfer.com/).
sergeynikitin wrote on Sun, 14 February 2010 15:42 There is a small problem with the translation Funding Ultimate++. In Russia, limited use of PayPal (perhaps not only in Russia). Perhaps there are similar international instruments? In Russia (and in post soviet countries) very common WebMoney (http://www.webmoney.ru/ or english link http://www.wmtransfer.com/). That is not a translation problem, it is a financing one And definitely, to get new financing sources is not a problem, is an opportunity
koldo wrote on Sun, 14 February 2010 20:08 Hello all Now Upp web is a little bit more international Could you find something different ? Menu looks great! Thank you for help, Koldo. About PayPal: Funding must be easier for users, more universal, have alternative ways of payment. Maybe, WebMoney is a good alternative. Best regards, Anton
Hello all Now translation links are in right side. As they are part of the T++ page, they have to be written and linked between them every time a page is done. Also in Forum these links are lost. I propose some new locations labelled 1, 2 or 3. These locations would be done automatically by uppweb so no language link would have to be included in T++. What do you think ?. What location do you prefer ?
koldo wrote on Mon, 15 February 2010 21:32 What do you think ?. What location do you prefer ? I would say the best position would be in the header (somewhere above position 3), but there is already google ad. From the suggested places, I think number 2 is the best. Best regards, Honza
Traditionally - Number 2! We - for the number 2! This the most logical!
Perhaps we put the notation language together with the flag?
sergeynikitin wrote on Mon, 15 February 2010 23:35 Perhaps we put the notation language together with the flag? Please, no flags! I know "a picture is worth a thousand words" but not in this case. Flags sometimes make sense for that country habitants but not for others. I would like to be able to know which is Russian translation without having to know it's flag. Languages abbreviations makes more sense than country flag, in fact we are talking about languages not countries so flags doesn't fit in language context. I don't see any correlation between language and flag. Andrei
In general, agrees. I do not insist on the flag. That would be just an artistic decision for me.
I don't know if this has anything to do with the translation efforts, but currently the "Manual" is broken. The context is cut after the packages heading.
cbpporter wrote on Tue, 16 February 2010 14:00 I don't know if this has anything to do with the translation efforts, but currently the "Manual" is broken. The context is cut after the packages heading. All works for me. P.S. Oops, you mean "Examples", not "Manual". http://www.ultimatepp.org/www$uppweb$examples$ru-ru.html - there I found them. Yes, English page is broken.
cbpporter wrote on Tue, 16 February 2010 09:00 I don't know if this has anything to do with the translation efforts, but currently the "Manual" is broken. The context is cut after the packages heading. Hello cbpporter Thanks for finding the bug. It was my fault. Problem is fixed so tomorrow morning Manual will appear in web as usual. When testing faulty version I checked the pages but I did not scroll it down so I did not realize it was broken.
Hello ScOrch Now I have realized of this: Quote: P.S. Oops, you mean "Examples", not "Manual". http://www.ultimatepp.org/www$uppweb$examples$ru-ru.html - there I found them. Yes, English page is broken. This has been caused because on Sunday I tested offline (of course) the changes. However at the same time the Examples page translated to Russian was uploaded. The problem is that as web Examples code has not been modified (internationalized) yet, it has taken the first Examples available option, that has been the Russian one Today I will retry to modify Examples code. If I cannot end it, I momentary remove the Examples Russian translation and Examples web will work in English properly.
Hello Andrei Quote: Please, no flags! I know "a picture is worth a thousand words" but not in this case. Flags sometimes make sense for that country habitants but not for others. I would like to be able to know which is Russian translation without having to know it's flag. Languages abbreviations makes more sense than country flag, in fact we are talking about languages not countries so flags doesn't fit in language context. I don't see any correlation between language and flag. Two possible focuses of this: - Wikipedia: http://en.wikipedia.org/wiki/Main_Page - GNU: http://www.gnu.org/
As Wikipedia - looks better and more appropriate
I vote for wikipedia style too. Another possibility would be a select box (or DropList in u++ terminology ). Honza
Hi, Wikipedia example is more usable, we don't have to scroll down to the bottom of page to change translation. If we implement that then [en][ru] links from translated pages should be removed if we have language selector "a la" wikipedia. Andrei
It would be good if there is no Russian articles, would automatically display the English version, and at the same site should not be completely switched to English. I do not know how to do this, maybe copied to Russian English text of article until will not be ready to translate into Russian.
sergeynikitin wrote on Wed, 17 February 2010 16:07 It would be good if there is no Russian articles, would automatically display the English version, and at the same site should not be completely switched to English. I do not know how to do this, maybe copied to Russian English text of article until will not be ready to translate into Russian. Hello Sergey That could be a brute force but effective solution. Now every web page is an .html so left buttons are solidly fitted to central page contents.
koldo wrote on Wed, 17 February 2010 16:15 Now every web page is an .html so left buttons are solidly fitted to central page contents. You can do dynamic effects in static html using javascript. But again, it is bad for SEO Another solution would be to use modrewrite on server to redirect nonexistent files to their english equivalent, but that would probably require using separate directory for each language in order to keep the language info. So Sergeys brute force solution is IMO the only solution that can be used right away Honza
Hello, Koldo! English page of Examples is still broken. Sorry, if you are already know about it. Best regards, Anton
Sc0rch wrote on Wed, 17 February 2010 20:30 Hello, Koldo! English page of Examples is still broken. Sorry, if you are already know about it. Best regards, Anton Hello Sc0rch The web infrastructure run once per day so we will have to wait until tomorrow to see the changes.
Hello all I think problems are fixed online. Thank you for your patience Now also Examples/References pages can be translated and thus Russian translations are used. Thanks to Mirek's good job it is not difficult to change web behavior. And after analyzing the causes of the problems you reported these week now I understand better how it works.
Hello all! Some pages translated. Screenshots (main and chameleon), Comparison with Qt, Applications. Added to SVN. Please, check them. Sorry, if something done wrong. Best regards, Anton
Dear friend! How to switch to Russian on page like this: http://www.ultimatepp.org/www$uppweb$overview$en-us.html ? (I can't find how to switch) Please return some language switch to any part of page.
sergeynikitin wrote on Fri, 30 April 2010 14:09 Dear friend! How to switch to Russian on page like this: http://www.ultimatepp.org/www$uppweb$overview$en-us.html ? (I can't find how to switch) Please return some language switch to any part of page. Hello Sergey Thank you for your comment. It was my fault in last change. I will commit the fix today.
Thanx!
Russian translation of Overview page is completed!
I propose to change mechanism of describe bazaar packages (and example packages). I tried to translate the page Bazar and faced with a challenge: List of packages rather variable. I propose following solution. If someone experienced - The description of the Linux applications are stored in files ".desktop" Here is a small piece of this file: [Desktop Entry] Encoding=UTF-8 Name=gitg Name[da]=gitg Name[es]=gitg Name[fr]=gitg Name[gl]=gitg Name[nl]=gitg Name[pa]=gitg Name[sv]=gitg Comment=Git repository browser Comment[da]=Arkivbrowseren Git Comment[es]=Examinador de repositorios Git Comment[fr]=Butineur de dépôt Git Comment[gl]=Examinador de repositorios Git Comment[nl]=Git repository bekijker Exec=gitg %U TryExec=gitg Terminal=false Type=Application Icon=gitg48x48.png Categories=GNOME;GTK;Development;RevisionControl; #X-GNOME-DocPath=gitg/gitg.xml As you can see, and the package name and description - multilingual. I also propose to modify the format of the package definition - file package-name.upp format using the same idea. And then the list of packages Bazaar can also be automated (as Examples) and the list can keep always up to date regardless of the chosen language.
Hello Sergey I think it is a great idea. A possible shortcut is to consider an .upp file someway similar to a .lay regarding to internacionalization. I mean, the message in .upp could be sent to the .t file when "Synchronize translation files".
sergeynikitin wrote on Thu, 24 June 2010 07:49 I also propose to modify the format of the package definition - file package-name.upp format using the same idea. Hi Sergey, It seems like an interesting idea. I think the description field in .upp files could be modified to store language specific strings. Application name is the same as the package directory name, so it would be a bit more complex and it is also not that important, but still possible. BUT... The main problem I see wit this proposal is the translation. No author knows all the languages, so he can't translate those descriptions by himself. A translator for given language could do that, but than he would have to have access to all the bazaar packages. Another option would be to submit each translated description to the package author separately, which would be tedious... Honza EDIT: I agree with Koldo, his solution is much better, I didn't see it before I sent my post One global .t file for bazaar packages located in uppweb would solve all the trouble.
I think it would be then ok to give everyone permissions to change .upp files, just like we can change .tpp now. Or maybe add some .uppt where only translation strings would be stored. (although generally I don't like clutter of project directories with obscure automated files (hey "init", did you hear me? ))