This is an unofficial Community project, unauthorized and without any connection to openSUSE, SUSE or any other Attachmate property. Content is subject to the original openSUSE copyright licensing This github repo may be cloned without restriction, but submitting significant improvements to the original repo is greatly appreciated.
In an effort to extend the reach of openSUSE, this project is only a DEMO of machine translation.
Only the content has been replicated from the original openSUSE pages, the underlying code hso been modified so cannot be considered a "mirror" or "clone of the original openSUSE pages.
Contact the Author and Project Manager through through the Github project pages or tsu2 through the Novell/Attachmate messaging system.
SDB System Upgrade SDB Zypper (To this Author's knowledge, although this page references a zypper version that is more than 2 years old, all the content should still be valid and reliable. Current zypper version in 12.3 is 1.8.12)
SDB KVM (Includes QEMU)
Chroot, systemd-nspawn, and installing OpenStack into a chroot SDB OpenStack Quickstart SDB DevStack
- If a non-enblish language web browser is detected, you should automatically be offered a translated page or - Find the Google Translate Widget in the top left of the page. Select your preferred language.
- All the content is frozen as of the moment the pages sere replicated. This means that if there are any changes to the original pages, those are not automatically reflected on these pages. But, if you do notice a change, popping a message to tsu2 on the Novell/Attachmate messaging system is appreciated (login to any openSUSE page, then send a private message)
- Only the pages linked directly from this page are translated Internal page links will work, but if a link to a location off the page is clicked, the User will most likely be taken to a page not on this site(usually back to opensuse.org).
Note that these pages are implemented with MACHINE TRANSLATION. No guarantee is made that any human being has evaluated the accuracy or clearness of translated text. In particular, although MACHINE TRANSLATION translates everything including what supposedly is seen on the machine, the machine will actually display according to whatever its language setting which may not be the same as your native language..So, USE AT YOUR OWN RISK.
Awhile back I had some discussions where experts opined that highly technical documents could not be translated, and any resulting machine translations were therefor worthless. Maybe, and these DEMO pages should show the current state of what might be possible with this technology. In any case, these pages might be the only resource for any that are not the officially supported languages.
I'm also curious whether something like this has value in at least providing a starting point before humans might fine tune for official versions.
- If an officially supported language version is available and accuracy is critical, don't use these pages. Even on these translated pages, usually a group of links can be found in the left Navigational pane which will take you directly to an officially supported version of the page.
- If you are a native speaker and you find some phrases aren't accurate, please use the Google options to suggest changes. Not only might the page itself be modified by Google, but other similar pages may be improved as well.
- If there is a page you'd like to have translated without submitting the page to an online Translator, suggest the page to me for consideration. On your suggestion I may deploy an automatically translated page for that as well.
- If you are a fluent native speaker who is willing to endorse the usability of any of these pages, pop me a message and spread the word! These pages are meant only to enhance available usable Public resources.
- Feedback! - Comments are needed whether these pages are helpful or not. Insturctions how to Contribute and Contact are near the beginning of this document.
What is Machine Translation and what are its drawbacks?
Machine Translation is what you might guess... The translation is performed by machine algorithm only. Unfortunately, human languages vary greatly in their linguistic syntax and structure so it can be difficult to create
Why this replicated website instead of a true clone or mirror? After some experimentation, I did not find a reliable way to overcome XSS (cross site sripting) issues. XSS has rightly been blocked in all recent web browsers due to the abuse and possibility of creating spear phishing attacks that don't just look like original websites but actually perform MITM attacks. The decision was also made not to deploy a full WikiMedia website, only static pages.
How was a working copy of the original page made? The original pages are deployed on WikiMedia which means that each page contains numerous references to external CSS and scripts. Simply copying the HTML is not adequate. The most current version of wget was used with options to collect all required external assets and re-write links for local only deployment. Curiously, I found that trying to replicate numerous pages at once fails, but retrieving one page at a time seems to work.
Why, how did you decide on the machine translation technology? Because all major web search engines need to support global languages for both querying and providing results, the biggest engines like Google and Bing have made their translation services publicly available at no cost. This is done so that Community can improve results by submitting modifications. And, hopefully this will not change any time in the near future. The alternatives suffer from a variety of problems, including more labor intensive contributions, a design that makes Community contributions less likely, limited resources compared to the major search engines.