My Windows Phone 8.1 application supports 2 languages and uses own localization system. I found 2 different ways to add the second language:
1) how to add a language in WMAppmanifest file for Windows Phone 8.1 and
2) http://www.jayway.com/2014/04/22/windows-phone-8-1-for-developers-localizing-apps/
I tried both:
1) edit Resources section in Package.appxmanifest
<Resources>
<Resource Language="en-US" />
<Resource Language="ru-RU" />
</Resources>
2) adding Strings folder with subfolders
Strings
en-US
Resources.resw
ru-RU
Resources.resw
but Windows Phone Dashboard doesn't detect any language besides default (en-US)
Have you ensured that the phone you are testing with has both languages installed?
Your app may support more languages, but if you don't set up the phone/keyboard for that language it will just let the user access the language it can.
This tool might help https://dev.windows.com/en-us/develop/multilingual-app-toolkit
Edit: also had to remember to not have empty resource files, need to have some (any) content in them to be found!
Related
In a Windows Phone 8 application you needed ID_CAP_VOIP to use
AudioRoutingManager.GetDefault().AudioEndpointChanged
What is the equivalent in a Universal Application? There don't appear to be any VOIP/Audio capabilities listed in the Capabilities tab on the Package.appxmanifest
(I'm starting to think this is impossible in an 8.1 Universal App)
Old question but now I know the answer.
Two things which you need to do:
1. Tag the audio in question as "communications"
How to do this depends on what API you're using. It could be as simple as . Or you might have to call IAudioClient2::SetClientProperties with an AudioClientProperties structure whose AudioClientProperties.eCategory = AudioCategory_Communications.
Tag your app as either a "voice over IP" app or a "voicemail" app
You should add file called WindowsPhoneReservedAppInfo.xml to your project with the following contents:
<?xml version="1.0" encoding="utf-8"?>
<WindowsPhoneReservedAppInfo xmlns="http://schemas.microsoft.com/phone/2013/windowsphonereservedappinfo">
<SoftwareCapabilities>
<SoftwareCapability Id="ID_CAP_VOIP" />
</SoftwareCapabilities>
</WindowsPhoneReservedAppInfo>
Look for more detailed explanation here:
Playing audio to the earpiece from a Windows Phone 8.1 universal app
I'm trying to create a simple camera application according to the MSDN tutorial.
All I did was installing Visual Studio 2013 Update 3 and then created a new Visual C# \ Store-Apps \ Windows Phone-Apps \ Empty App Template and added the code to my MainPage.xaml.cs.
The first problem is, that it does not find the namespaces Microsoft.Xna.Framework.Media, System.IO.IsolatedStorage and Microsoft.Devices. According to the tutorial, I have to add the Xna DLL in the "Add references" .net Tab, but unfortunately, there is no .net tab. I only have the following categories:
-Assembly (All Assemblys are already references)
-Project
-Windows Phone 8.1 (only 5 DLLs, but different ones)
After a lot of searching, I found them in 'C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\Tools\AppDeploy\MdilXapCompilev8.0\Framework', but there is no System.IO.IsolatedStorage DLL.
When I ommit this using directive, I end up getting an error because it does not know this.Dispatcher.
Am I missing something? Do I have to install anything else?
The problem is probably that the link you have provided concerns WP8.1 Silverlight and you might have chosen WP8.1 Runtime project. Those are different API's - XNA is not supported in RunTime, you also won't find Microsoft.Devices there.
If you want to create your Camera App for WP8.1 Silverlight encure that you have chosen (Windows Phone Silverlight) template. Otherwise, of course you can also write Camera App but with different API - you may take a look here,also you may find something useful here at blog.
I have created a Win32 project for it according to this document and imported Italiona, Turkish and neutral DLL's to my WP application. Neutral is running correctly but when I chnage my emulator's or phone's language, title and tile title don't change.
What can be it's reason?
Thanks.
In Windows Phone 8.1 Win-RT you do not need a dll.
Here's a set of screenshots as a step by step guide:
http://s27.postimg.org/nz4xweo7n/Localize_App_Name.png
Make sure that you've add the control you wanted to change(In your case the Title) through the AppResources.resx of the respective language.
This should help you. Refer this one too.
http://www.c-sharpcorner.com/UploadFile/manish1231/windows-phone-8-app-localization/
http://msdn.microsoft.com/library/windows/apps/ff637520(v=vs.105).aspx
Hope it helps!
Try this post, It explains in detail how to localize your app quickly and easily.
You need to add Key Value pairs to the AppResource.resx file in the Resources folder. The values should be the Strings you need to translate to other languages and the key is used to call them in XAML or in code.
Install Multilingual App Toolkit and enable it in VS.
After you added the strings to the AppResources.resx file, you can use Multilingual App Toolkit to generate the other AppResources files for each of the languages you need to translate.
Then you can use Multilingual App Toolkit editor to either translate them automatically using Bing Translate or you can do it manually.
I tried to localize my app title using the WP7 AppResLib DLL Generator and it partially work. After installing, the application title in the application list adjust well to the phone's language. For now two languages are supported: Polish and English.
Unfortunately, the application title in the Windows Phone Store is always displayed in English (no matter which language is set as a phone language or which version of the Store's website I visit).
In the root folder of the project I have the following files:
AppResLib.dll
AppResLib.dll.0409.mui (0409 - English (United States))
AppResLib.dll.0415.mui (0415 - Polish (Poland))
And that's how my WMAppManifest.xml file looks like:
<?xml version="1.0" encoding="utf-8"?>
<Deployment xmlns="http://schemas.microsoft.com/windowsphone/2012/deployment" AppPlatformVersion="8.0">
<DefaultLanguage xmlns="" code="en-US" />
<Languages xmlns="">
<Language code="en-US" />
<Language code="pl-PL" />
</Languages>
...
</Deployment>
Can anyone tell me why it doesn't work as expected?
Remark:
Solution provided in the Microsoft's article How to localize an app title for Windows Phone 8 didn't worked for me, since I had problems with compiling the resource project both in VS2012 Express for Windows Phone or VS2013 for Windows.
When reading about WP8 C++ project template, I see
Windows Phone Empty Dynamic Link Library
A project for creating a native dynamic-link library for a Windows
Phone app.
Windows Phone Empty Static Library
A project for creating a native static library for a Windows Phone
app.
What are static library and dynamic link library mean to WP8?
Supposed I have my Windows library source (openssl for example), do I need to convert to WP8 static library to be consumed by WP8 apps?
Whether I use WP8 static or dynamic link library, I must wrap them in WP8 runtime component in order for my app to consume, am I right ?
At the basic level, static and dynamic libraries are the same as any other Windows environment (so see this other SO question for more clarification).
For a WP8 app you will either need to produce:
A XAML .NET/Windows Runtime hybrid app.
A DirectX C++/C project (usually a game).
For 1. you would need to wrap up either your static .lib or .dll in a WP8 Runtime component, for your .NET side to consume.
For 2. it looks like you end up building a traditional .exe. In that case you would link directly to your .lib or .dll in the normal way. (I not so familiar with this one, so may be missing some subtleties here).
In any case it's easier to link everything if you have all the source code in VS and reference the projects that build .lib or .dll you need, rather than the referencing the binaries themselves.
That way you can ensure all the code is built to target the correct runtime environment (targetting the Phone APIs, using the correct CPU architecture). Also VS should then automatically add all dependencies into your final XAP package.