Does Dialogflox CX support agent in Arabic language ? The language support documentation mentions Arabic (preview) Text support. I am not sure what preview means here. How to accomplish a english/arabic language chat bot best using dialogueflow CX, please explain.
Yes, Dialogflow CX does support Arabic language, you would just need to specify it when you create the agent as show below.
Yes, you can test and use the ar- Arabic language in Dialogflow CX.
According to the Product launch stages documentation, at the Preview stage, products or features are ready for testing by customers. Preview offerings are often publicly announced, but are not necessarily feature-complete, and no SLAs or technical support commitments are provided for these. Unless stated otherwise by Google, Preview offerings are intended for use in test environments only. The average Preview stage lasts about six months.
If you want to use multiple languages in a Dialogflow CX agent, you can add additional languages in the Agent settings > Languages tab. The language you choose when creating an agent is set as the default language. For the complete list, see the languages reference page.
Note that the requests to the agent should contain a language code to match intents of the desired language. If not specified, the agent's default language is used.
Related
i am working on a bot project with Microsofts Bot Framework. My bot is based on the SDK 4.0 and until this point, everything is working fine. In the last few days was thinking about making a change and go and use the BF Composer to configure and build my bot solutions.
After some tests i discovered, that the availible bots inside the Composer are only available in the english language set. But my bot uses german as the default language.
Now to my question:
Is it possible to set Bot Framework Composer Bots to a diffrernt lanugage than english (german for example)? If not, when will this be availabe?
Composer already supports authoring bots in different languages. The documentation on multiple language support should get you started. You can combine this with support for different cultures in LUIS and QnA to create bots in languages other than English.
Is it technically possible to use the plugin Microsoft Find Time for an iframe embed to schedule a Microsoft Teams meeting together in a Microsoft Outlook calendar with other accounts using external e-mail addresses?
What other free or commercial tools come to your mind for such a use case, preferrably with location in EU and fully compliant to EU-GDPR with a template of what to add in the data privacy statement.
One tool I already know, but which can't be customized enough for the given use case is Appointlet.
Also, a Microsoft Bookings licence is currently no option.
Are there equal or better alternatives?
Kind regards and thanks,
I am creating an application, and I noticed that nowhere can i find text such as 'pin to start' to use for livetiles in my application (creating a secondary tile). I tried to send Microsoft's AppHub a support ticket, but I only received a response saying that I could not be helped with translations? I clearly stated the need to be standardized and uniform across my third party apps and default behavior, but this had no effect on the answer. My problem arises when I translate my applications using a resx translator tool and Bing for my translation service. Some words to not translate correctly, which is fine because I go back through to check and then attempt to do this manually, but phrases such as 'pin to start' which are so unique to the WP7 application list sometimes do not translate properly at all. I would like to be as close to Microsoft's default language translations as possible for supported display languages, but are there any resources which may help me out? Or am I left in the dust to try to figure these out myself?
There is a page Microsoft Terminology Collection where you can download sets of standard texts.
There is no document that will show you the localized versions of the system strings. For that, you will have to dig through OS files, and that implies that you will have access to the WP OS image. You have to rely on your own translation skills or simply switch languages on the phone to check specific strings.
I looked through MSDN and couldn't find a clear cut answer to this one. So, if i'm building a localized WP7-application, should i conform to phone's language/culture settings or can i roll my own language/culture-switching mechanism inside the app?
Here's the relevant section from MSDN: http://msdn.microsoft.com/en-us/library/ff637522(v=vs.92).aspx
This is stated in "Testing Your Application":
When changing a display language, verify that the language of your
application UI automatically updates to that language.
Should this be taken as a "soft" guideline or a precondition for Marketplace acceptance?
ps. I know that this question is pretty academic in nature, because i cannot think of any scenario where standard localization mechanism wouldn't be enough.
Edit:
To clarify my point: If i build a localized/globalized app, am i required to or should i use the phone's settings or can i implement my own culture switching?
You would have to perform this sort of test on a real device, by navigating to settings > region + language. In this page you can change language and other locale information such as date format.
I'm not sure, but I guess a developer may implement "own" language switching mechanism inside the app. One example is: I have English choosen as a device language but Czech as region I live. I don't want to see whole OS in Czech but I would like to see one specific application (which supports Czech) in Czech language. It means, without switching OS to Czech this cannot be provided. For this scenario, I think, is the best to have a possibility to choose the language in the app as well - so I can stay in English OS language and I can switch this app to Czech.
I'm developing a WinForm app in c# 4.0 and would like other (non-developer) colleagues to contribute writing a context sensitive end-user helpfile. First I thought I could use "HTML Help Workshop" from Microsoft, but it seems outdated (Vista and Windows 7 not supported).
Then I've looked at Sandcastle, but the documentation is lacking and I wonder if it is suitable for non-technical users to write end-user documentation.
So I read about RoboHelp, but it's way to expensive for me.
I'm getting lost in all the information that is available about helpfiles. Can someone help give some best practices or information on what tools to use and what output format I should target (still chm or other).
Great question. I like your idea of non-developers contributing to the end-user documentation.
This idea might motivate users and testers of your application to easily contribute to the documentation.
The first thing that comes to my mind, is using a some sort of wiki engine. You could build a simple function in your WinForm application, that fires up a browser and directs in to the wiki. You could use the context from which it is called to build up an url; e.g. http://dev-wiki.mycompany.com/LoginForm?action=edit. Here the name of the form ("LoginForm") is used in the url of a wiki page.
Alternatively, you could simply use the embedded web browser control for WinForms to access the wiki. That would look something like:
var url = GetWikiUrl(myForm);
browserControl.Navigate(url);
This would be very easy to embed in your application.
In a controlled (office) environment, this would be very easy to set up. In you production environment it might be a bit more difficult, but still doable. It might leverage some end-user contributions too.
For writing documentation, I use sphinx.
It lets you document in plain text and has various output formats (chm, html, pdf etc.).
Some of these (chm, html) can be used as context-sensitive help sources.
However simple, the sphinx user-interface (text editor and make file) might not be suitable for non-technical users.
I would recommend to use Help+Manual for creating CHM documentation. It's similar to MS Word and any PC user can start to contribute doc development after short education.
But this tool isn't free :(