Microsoft Edge Insider. Azure Databases. Autonomous Systems. Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work. Small and Medium Business.
Humans of IT. Green Tech. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Show only Search instead for. Did you mean:. Sign In. Adding Local Experience Packs to your Windows image. Pankaj Mathur. Ever since the Insider builds that contained the new, re-written from scratch Touch Keyboard in , Shape-Writing has not worked once.
The announcement of support for Shape-Writing in all English speaking countries except Australia can be found here in the blog post for build , Windows 10 version But no words appear in the Word-Flow above the keyboard or in the text input box you have selected to type in. Side note, the Word Flow that suggests words as you type didn't work at all in It started to work in but only works inconsistently.
The Word-Flow may not appear at all on random occasions, even in and So it too is buggy and needs fixing. Since the new , re-written from scratch Touch Keyboard was added in , the Dictation Microphone button with English Australia as the Display Language, does not appear. Doing so does not start Dictation and nothing happens at all. I do understand that late in development you added a note within Ease of Access Settings that the "Talk instead of type" states it is US English only, but why are we going backwards here?
Why is there such a huge disconnect here? The speech recognition is in the language pack, but isn't available to the system except for Cortana?
As you can see, this is a comprehensive list of missing and broken features for Australia. Each item of missing features, broken and buggy features and undesired behaviour of Windows 10 that I have listed here, I have submitted Feedback for in the Feedback hub multiple times over the past year.
Other Australians have submitted Feedback on these issues too and we've all upvoted it. Why is Microsoft ignoring us Aussies? Why are we being treated so incredibly poorly with our Language pack? Missing and broken functionality that we're reporting but you're ignoring. I have been patient and informative, I've provided logs, screenshots and reproduction captures in the Feedback hub and it's all being ignored. Noone from Microsoft has even acknowledged any of these issues.
Can we as the nation of Australia please be heard? I look forward from hearing back from a real Microsoft developer from the Language team on all of this. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. Every single issue I outlined in the original post is present on every machine, across multiple accounts both Microsoft Accounts and Local. And as I state in the original post, all issues have been present since through to the latest insider build of Multiple Feedback Submissions and upvotes, all ignored by Microsoft.
These are severe issues affecting all Australian Windows 10 users, going unchecked and it's really frustrating that we're not being heard. Deploy the new reference image and after a domain user logs in verify that you have the English Australia language pack installed and most importantly that the indexing service has correctly indexed the control panel and other items that normally would have failed.
It looks like W10 has a global problem with the Aussie language pack, as it is part of the UK pack install. Hope someone smarter than me, and with more time on their hands, can solve it. As of , the en-AU language pack no longer has a dependency on the GB language base and can be added to the en-US installation media. However, The component that wasn't supplied by Microsoft is the en-AU System UI package which is the "Display Language" package, and also the handwriting packs.
I have tested an image using en-GB as a base, and I have had more problems with that, than using en-US as a language base. Thank you, Luke.
0コメント