I am creating a bot service which can talk in any supportive language. My question is if the person started in English to chat and in middle he is not comfortable with English and want to change to Spanish or French. I would like to give that feature.
Is there any possibility to change the language of the bot in middle?
Any one faced the same issue helped is a great thing.
Thanks in advance.
The logic wants to develop is appreciated, unfortunately such type of middle changes of languages in not yet supportive. Instead, create the bot, that will ask for language change if needed and take the response. If the response is "YES" then give the feasibility to the user to change the language. But the conversation up to that point happened cannot be converted. It is too complex to think.
For language supportive check: https://support.microsoft.com/en-gb/office/microsoft-teams-supported-languages-for-help-content-9c71d10a-0c5c-49d4-b6d7-0c58cdfdf4cf
Related
I am planning to design a google action, which will help users to learn some phrases in another language lets say "French". Here is an Example:-
“ok google, let me talk to learn french”
LearnFrench (LF): Hi! This is learn french! Would you like to practice 20 of the most important basic phrases in speaking French?”
user: “Yes”
LF: “Great! I’ll start by telling you a word in French - and you repeat after me. Let’s start with bonjour.
user: bonjour
LF: that was good! Bonjour is the most common greeting you’ll need. Next is "bonsoir" / or let’s try that again, it didn’t quite sound like “bonjour”
user: bonsoir
LF: bonsoir is used as a in the early evening,
etc….continues through 20 or so phrases. After going through those then there could be some type of “recall” practice. LF would say the phrase in English and the user would say the phrase in French. And if the user says it incorrectly then LF “learns” the phrases that the user needs to improve on.
At the end of a session LF would say something like “I think you know the basics here - good luck on your trip”.
If after that session the user came back to LF - LF would know that the user had already come before and would ask if they want to repeat the tutorial - or ask if they want to move straight to the quiz.
Is it possible to have multiple language support?
While Google Assistant is available in other languages, the Actions on Google platform is currently only available in U.S. English and U.K. English. We’re working to make Actions on Google available in other languages, but we don’t have a formal release date. We’ll make announcements to the community with updates as they occur.
If you are already using the invocation name, it is not possible to link it to another project/app.
Thanks,
Actions on Google Support Team
Thank you in advance for reading this. Here is the situation. I have been working on a online guitar shop using Magento CE 1.7 for several months. I greatly underestimated the cost of the site and I know that is my fault not the client who by the way is a great guy. There where many issues that took a lot of time including having to move it from a testing server to the real domain, many logo tweaks etc. I am almost done with it and really need to “stop the bleeding” so to speak however there is one feature that he really wants that I am at my whits end with.
Its a custom order form for guitar pickups. He had one on his old site that was don’t in ASP and besides not knowing ASP we are now on a Unix server.
His requirements are “the ability for someone to choose a category (ie: 7-string, Strat Replacement, Tele Replacement, etc) , and then have it be able to only show options that are applicable to what that selection. I want customers to be able to see descriptions of each pickup somewhere on this page. I also want people to be able to see what the covers/colors look like when they choose that.”
I was able to use the way back machine to at least show you guys what he wants, here is the link http://web-beta.archive.org/web/20120127233223/http://www.axepalace.com/pickup_order.asp
Here is my attempt to create it with a product with lots of options. http://axepalace.com/pickups/bare-knuckle/bkp-order-form/bare-knuckle-pickup-order-form.html
So could anyone please give me some feedback / suggestions. My sanity would really appreciate it!
I was just wondering about the pros and cons of submitting metadata and changing the UI buttons for people who don't speak English.
According to this study there isn't a huge percentage of users who go to stores that aren't in English (all the smaller countries have stores in UK English).
That said, I was wondering if maybe there is some advantage to this? For example, if I submit to the French store I would assume there are less apps with metadata in French and so therefore you might have a better chance of getting featured.
Keep in mind my app is super simple with no network activity and only a couple of buttons I would need to translate.
PS please forgive me if this is not an appropriate question for this site. And feel free to vote to migrate.
There is no disadvantage of providing localised versions of your application. It's probably more a question of knowing your target audience.
Generally one should assume that in a country, which official language is not English, people don't speak English. Of course there are exceptions like Germany were a lot of people do speak English. But usually they still feel more comfortable using their native language. Following your example, French traditionally have a very strong opinion when it comes to languages and will appreciate a French localisation.
Besides users by country you should also take into account the area or business segment you're targeting. Just to give an example: an British pub guide obviously is targeting English speaking people. If you're creating something around renewable energy it could be worth exploring a German version besides an international English one, too since it's really popular in Germany and also supported by government subsidies.
If you can reach your potential users in English a localisation might not be necessary. But the lack of localisations will make it definitely harder to advertise your application. I can't think of an non-localised app have been featured on the German App Store. This might be just bad memory but Apple points out the importance of localisations many times in the documentation.
Since you mentioned your application doesn't actually have that many localisable elements it might be worth the effort anyway. Even if you decide not to do so for the initial release it's worth building your application with future localisation in mind to add localisations in later updates. See that post for more.
There is a disadvantage, and it is that once you add a language, you will be expected to continue supporting it in future releases. It's not nice for someone who uses your app in say Chinese to install an update and find that the app has reverted to English or that some new features are not translated. But in order to continue supporting a language in future releases, you'll have to get new/changed content translated which will cost you (assuming you are paying a translator) and delay your release a little. You'll also have a bigger testing burden.
That said, localization is a great way to attract more users.
I'm wondering if there's an off the shelf CMS available that is similar to something like Mobile Roadie - ie: it will allow you to create multiple versions of one application? I'm looking to develop some mobile travel guides for iPhone/Android/Blackberry etc, and rather than get a CMS built, I'd like to see if there's something out there is similar to Wordpress in that it will allow us to input text, images, Google Maps details, phone numbers, email addresses and potentially some audio/video content.
If anyone knows of anything, I'd love to hear about it. Also, if you have any ideas regarding pricing, that would be extremely helpful! Thanks in advance for your assistance.
The chances of you finding something "Off the shelf" diminish as your requirements get more specific. You want something for a limited and specific target audience (iPhone, Andriod, Blackberry) that can deliver many different types of very specific content (addresses, maps, text, images, video).
From my experience of building a CMS for one of the world's most famous travel guides, I can say your chances are slim indeed. The technical requirements of managing this type of information are huuuuuge!
But hell, I could be wrong! I hope you find something that solves your problem and you make the world a better place!
PS: Maybe you should simplify your requirements and build from there? Good luck. :)
I just dropped a reply on this question:
How to setup a CMS as a backend for iPhone app
You could look at this blog for a drupal showcase:
http://drupal.org/node/900630
and at this wordpress plugin:
http://wordpress.org/extend/plugins/json-api/
Personally I am trying with tikiwiki.org but I am not sure yet if it is right.
Cheers
We created a very flexible CMS called StorageRoom which we built specifically for mobile apps.
You could easily let users manage locations with maps and additional fields.
As I'm starting to develop for the web, I'm noticing that having a document between the client and myself that clearly lays out what they want would be very helpful for both parties. After reading some of Joel's advice, doing anything without a spec is a headache, unless of course your billing hourly ;)
In those that have had experience,
what is a good way to extract all
the information possible from the
client about what they want their
website to do and how it looks? Good
ways to avoid feature creep?
What web specific requirements
should I be aware of? (graphic
design perhaps)
What do you use to write your specs in?
Any thing else one should know?
Thanks!
Ps: to "StackOverflow Purists" , if my question sucks, i'm open to feed back on how to improve it rather than votes down and "your question sucks" comments
Depends on the goal of the web-site. If it is a site to market a new product being released by the client, it is easier to narrow down the spec, if it's a general site, then it's a lot of back and forth.
Outline the following:
What is the goal of the site / re-design.
What is the expected raise in customer base?
What is the customer retainment goal?
What is the target demographic?
Outline from the start all the interactive elements - flash / movies / games.
Outline the IA, sit down with the client and outline all the sections they want. Think up of how to organize it and bring it back to them.
Get all changes in writing.
Do all spec preparation before starting development to avoid last minute changes.
Some general pointers
Be polite, but don't be too easy-going. If the client is asking for something impossible, let them know that in a polite way. Don't say YOU can't do it, say it is not possible to accomplish that in the allotted time and budget.
Avoid making comparisons between your ideas and big name company websites. Don't say your search function will be like Google, because you set a certain kind of standard for your program that the user is used to.
Follow standards in whatever area of work you are. This will make sure that the code is not only easy to maintain later but also avoid the chances of bugs.
Stress accessibility to yourself and the client, it is a big a thing.
More stuff:
Do not be afraid to voice your opinion. Of course, the client has the money and the decision at hand whether to work with you - so be polite. But don't be a push-over, you have been in the industry and you know how it works, so let them know what will work and what won't.
If the client stumbles on your technical explanations, don't assume they are stupid, they are just in another industry.
Steer the client away from cliches and buzz words. Avoid throwing words like 'ajax' and 'web 2.0' around, unless you have the exact functionality in mind.
Make sure to plan everything before you start work as I have said above. If the site is interactive, you have to make sure everything meshes together. When the site is thought up piece by piece, trust me it is noticeable.
One piece of advice that I've seen in many software design situations (not just web site design) relates to user expectations. Some people manage them well by giving the user something to see, while making sure that the user doesn't believe that the thing they're seeing can actually work.
Paper prototyping can help a lot for this type of situation: http://en.wikipedia.org/wiki/Paper_prototyping
I'm with the paper prototyping, but use iplotz.com for it, which is working out fine so far from us.
It makes you think about how the application should work in more detail, and thus makes it less likely to miss out on certain things you need to build, and it makes it much easier to explain to the client what you are thinking of.
You can also ask the client to use iplotz to explain the demands to you, or cooperate in it.
I also found looking for client questionnaires on google a good idea to help generate some more ideas:
Google: web client questionnaire,
There are dozens of pdfs and other forms to learn from