Category Archives: Full text scroll for Search and Read
Resource Translation Utility
The Resource Translation Utility enables you to quickly translate any KWizCom add-on for SharePoint 2010/2013 to any required language, by using the Microsoft Translation Services.
(Actually, this utility translates Any .NET resource file)
To start using this utility, you need to:
1. Run it on a machine that has internet access.
2. Get an account on Windows Azure Marketplace (so you’ll be able to use the Microsoft Translation Services)
- Download this Free utility and unzip the file on your PC/Server.
- Download the User Guide.
- Run the.msi installation file to install the utility.
The Microsoft Translator API is accessible through Microsoft Windows Azure Marketplace. You can see it here: https://datamarket.azure.com/.
To begin developing using the Microsoft Translator API, you need to do the following:
- Register for an account on Windows Azure Marketplace.
- If you already have an account, you can use it, but it’s recommended that you follow through these steps to ensure that you configure the service correctly
- Sign up for the Microsoft Translator API using your registered account.
- Register your application on Windows Azure Marketplace.
- Get the Client ID and Client Secret for your registered application.
The following instructions will show you how to do this. When you’ve completed them, you’ll be ready to start coding.
Sign-in to Windows Azure Marketplace. If this is your first time, you’ll likely see this registration page.
Fill out your details, and press the ‘Continue’ button.
Once you’ve done this, you’ll be taken back to the main Windows Azure Marketplace webpage.
In this section you’ll subscribe to the Microsoft Translator API in the Windows Azure Marketplace. There are a number of service options you can choose, and in this walkthrough you’ll see how to use the free one.
If you’ve completed the Windows Azure Marketplace registration (Step 1), then visit https://datamarket.azure.com/ to see the main Marketplace home page. At the top of the screen, you’ll see a ‘Search’ box.
Type ‘translator’ into this box and press enter, or click the button on the right that is shaped like a magnifying glass.
In the search results, you’ll see the Microsoft Translator API:
Click on ’Microsoft Translator’ and you’ll be taken to the Microsoft Translator API Offer page on Windows Azure Marketplace.
(Note: For a short cut, you can also go directly to the screen by visiting this URL: https://datamarket.azure.com/dataset/bing/microsofttranslator)
On the right hand side of the screen, you’ll see a number of different monthly volume offers. Choose the one that meets your monthly volume usage needs. For this guide, you’ll use the free 2 million characters per month subscription offer, which you can find at the bottom of the list.
If you agree, check the box and press the Sign Up button.
You’ll then be taken to the page confirming that you’ve successfully subscribed to the service and the volume goes into effect at that time. In the next step, you’ll get your developer credentials from Windows Azure Marketplace, and you’ll use these when building your apps.
This step assumes that you have:
· Completed Steps 1 and 2
· You have registered for a Windows Azure Marketplace account
· You have used your Marketplace account to subscribe to the Microsoft Translator API service.
Sign in to https://datamarket.azure.com/, and you’ll see the familiar welcome page.
At the bottom of the page, you’ll see a number of links, organized into columns.
One of these reads ‘Develop’, and under it you’ll see a link that says ‘Register your Application’.
Select this and you’ll be taken to the screen that allows you register your application.
You use this to get the Client ID and Client Secret values that your application will need to authenticate your service when you build your application.
· Fill out the Client ID, and Name fields.
· The Client Secret field is already completed for you. Do not change it.
· Fill out the ‘Redirect URI’ field with any valid URL that uses https, for example https://microsoft.com. This field is not used by the Microsoft Translator API.
· You can also leave the ‘Enable subdomain access’ checkbox unchecked, as Translator doesn’t use it.
Remember and note the Client ID and Client Secret fields. You will need these when you write your app.
Here’s an example:
If, in the future you want to create new apps, you can go straight to this screen: https://datamarket.azure.com/developer/applications/register
To see a list of the apps you have on Marketplace, and see their Client ID and Client Secret visit: https://datamarket.azure.com/developer/applications and press the ‘Edit’ link to see the details for your app.
Next, you’ll be taken to a page containing the list of your applications. (Note: For future reference, here’s a shortcut: https://datamarket.azure.com/developer/applications)
You should see your application at the bottom of this screen, like this. If you want to change the Client ID, you can do so from the ’Edit’ link, or you can register new applications with the Register button.
Creating an ASP.NET Web Application
If you don’t have Visual Studio, you can use the free Visual Web Developer Express from Microsoft to create ASP.NET pages. It can be downloaded from here: http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-web-developer-express
The first step is to create a new Project, and in the project types dialog box, select ASP.NET Web Application and call it FirstTranslator. Make sure that you selected ‘.NET Framework 4’ as the version of .NET you are using.
Tham khảo link sau để sử dụng: http://blogs.msdn.com/b/translation/p/gettingstarted2.aspx
DAISY for All Project
Welcome to the DAISY for All Project pages. Here you will learn about the project, our accomplishments thus far, the latest news, and how you can participate.
DAISY(Digital Accessible Information System)
DAISY (Digital Accessible Information System) is an open international standard for accessible multimedia. The DAISY Consortium is set up in Switzerland by leading not-for-profit organizations from around the world serving blind and dyslexic people in order to develop and maintain the standard.
Accessible multimedia is ideal for people with disabilities as well as for the general public to share information and knowledge world wide. DAISY helps bridge the digital divide in developing regions of the world and to ensure access to information for the information disadvantaged, such as people with print disabilities, language minorities in a community, indigenous populations who do not have their own script, and those who are illiterate.
DAISY for All (DFA in short) will deploy DAISY technology and address goals and objectives which include capacity building in developing countries and to serve as a catalyst to generate broader alliances supporting the global sharing of human knowledge in the information society. DAISY for All is funded by the Nippon Foundation as a five year project.
DFA has two resource centers: one in Bangkok, Thailand, and one in New Delhi, India.
The DFA Project has established 8 focal points excluding 2 resource centers in India and Thailand.
Fiscal Year 2006
- The Philippines
Fiscal Year 2005
Fiscal Year 2004
- Sri Lanka
Tổng kết qua báo cáo năm 2006 của Daisy for All:
Venue: National Association for the Blind, Sector 5, R.K Puram, New Delhi-110022.
Dipendra Manocha (firstname.lastname@example.org)
Assistant Project Manager in New Delhi
AMIS Development Activities
- AMIS Internationalization and Localization Meeting, Tokyo, Japan
January 23, 24, 2006
- AMIS Translation Workshop in Delhi, India
April 10-15, 2006
AMIS was localized for Vietnamese, Indonesian, Bengalese, Tamil, Urdu and Arabic
- AMIS/Ambulant Working Session in Amsterdam, Netherlands
July 17-19, 2006
- AMIS 2.5 Release
November 2, 2006
- AMIS-Ambulant Working Session in Amsterdam, Netherlands
November 10, 13-14, 2006
Download source và phần mềm AMIS tại đây: http://www.daisy.org/amis/need-help-amis
Highlights: DAISY For All (DFA)
All DAISY For All Project activities are generously funded by the Nippon Foundation.
Additional focal points were established in Asian developing countries, International Trainers Training seminars for DAISY Production were conducted, and a new version of AMIS, the open source DAISY player being developed by DFA was released in 2006:
The goal of the DAISY OK Project is to define what “DAISY OK” is and how it can and should be applied. The primary purpose of the DAISY OK Project is to encourage both Reading System developers and DAISY book producers to create products that provide a truly enhanced reading experience. DAISY OK requirements that describe and define both a conforming DAISY Reading System (player) and a conforming DAISY book were developed and made available in August 2006. Both required functionality and advanced features were identified. Online DAISY OK self-certification for Members and Friends of the Consortium will be available in 2007.
March 27 – 31, 2006
Conducted by Miki Azuma and Raksak Chairanjuansakun
The training was undertaken with the aim of achieving the following goals:
The focal point in Vietnam was established in March 2006.
November 24, 2005. Hanoi, Vietnam
Hiroshi Kawamura and Monthian Buntan organized the workshop.
Mr. Julien Quint, Mr. Daniel Weck & Ms. Marisa DeMeglio were the resource persons for this workshop. Mr. Dipendra Manocha looked after the logistics arrangements for the workshop. The resource persons had produced the web-based prompt translation modules and structures for recording the prompts and help books. The audio recording was done using Sigtuna DAR 3 . The resource persons produced script to convert the prompts and help book projects into language packs. A new version of AMIS with enhanced self voicing features and support for the new format of the language packs is being prepared for the release. This version of AMIS will be called 2.3 and will be released along with the new language packs.
The text for the document to be translated were sent one month before the date of the workshop. The language translation work was done for some languages on payment basis and for others through voluntary contribution. In most of the cases, the language translators attended the workshop for the production of final language packs. The following persons had been language translators / workshop participants for each of the languages.
|Hindi||Dr.Dipendra Manocha||Mr Ajay Mathur and Mr. Sandeep Kaler|
|Vietnamese||Dr.Le Toan Thang & Mr.Hoang Moc Kien||Dr. Le Toan Thang & Mr.Hoang Moc Kien|
|Arabic||Mr. Abdul Malik||Mr. Abdul Malik & Mr. Prashant Ranjan Verma|
|Indonesian||Mr.Nassat D Idris||Mr.Achmad Hikam and Ms. Deepika Sood|
|Urdu||Mr.Aqeel Kureshi & Mr. Tanuj Malik from M/s Technocom||Aqeel Kureshi, Dr. Saira, Ms Deepika Sood and Mukesh Sharma|
|Bangla||Mr.Vashkar Vattacharya & Mr. Habib||Mr.Vashkar Vattacharya & Mr.Habib|
|Tamil||Mrs.Sreeja||Mrs.Sreeja and Mr. Anubhav Mitra|
Challenges & Highlights
- Sigtuna DAR 3 does not support display of Unicode characters. The resource persons had to use conversion of characters into entity representation for correct display of text content. The headings view in Sigtuna DAR 3 (sidebar) was unable to display Unicode characters, and showed only question marks.
- Two languages, Urdu and Arabic, were introduced which have right to left script direction. These languages were successfully incorporated in the language pack format.
- AMIS requires additional work in order to re-orient its user interface to accommodate right to left scripts. While the script’s characters are already supported and displayed from right to left, the entire user interface (e.g., menus, navigation lists, and toolbars) should all start from the right and flow left.
- Due to ill health, Mr. Aqeel Kureshi could attend the workshop only for one day. The work of Urdu was completed with the support from NAB staff and the resource person invited from Jamia Milia Islamia University who kindly agreed to provide support without any prior notice.
- Language packs from the 2005 DFA AMIS workshop require upgrading before they can be used in AMIS version 2.3 and higher. These upgrades will be partially completed by the DFA resource persons. Full completion requires the involvement of focal point experts.