It occurs only in 'problems' section and only while I am using C#
I tried to change the display language to en, but it was already like that. I also tried to use a command to change cultureinfo to en-US, but I haven't seen any results
Related
I have a document-based application with 3 document types (Type A, Type B, Type C) configured as editor in the info.plist. How can I make it so that Type A will allow the user to set whatever file name they want when saving, without forcing any particular extension, while still being able to choose from the 3 different formats?
What I’ve tried:
Setting the NSSavePanel’s allowsOtherFileTypes to true in my NSDocument’s prepareSavePanel() function. This isn’t sufficient because it only works if the user enters an extension that isn’t currently known by the system (e.g. “My document.foo” will still save as “My Document.foo.typea”).
Not setting a type identifier on the document type in the info.plist. This actually worked reasonably well up until macOS 13, where it logs an error about a UTI that wasn't exported and won't offer that type in the save panel.
Setting a blank extension on the exported type in the info.plist. This almost works but if the user enters a known extension it shows a prompt like this:
You have used the extension “.txt” at the end of the name. The standard extension is “.”.
Not setting any extension on the exported type in the info.plist. This seemed to work great on macOS 13, but on macOS 12 it would show a prompt similar to the above but with “.(null)” rather than “.”.
So, without completely overriding the entire save process, I'm now out of ideas.
I had another idea which seems to be working on both macOS 12 and 13:
Set the type identifier of the document type to public.data in the info.plist.
On macOS 12 this logs a warning about not having a valid extension, but it doesn't show any confusing prompts to the user. I'm still open to other solutions though, if anyone has any.
I'm quite new to the world of google home/assistant, but I've tried out the new Actions builder, which seems really good and intuitive. I have added the methods of invocation, an intent that triggers an inline webhook function, and filled out all the mandatory fields under "Deploy" for both languages. Testing works as expected in simulation (except not in my native language, Norwegian).
But when I try to create an alpha release, it says "Missing info", and that i should navigate to the "Overview" to see what's missing.
I head over to the overview only to see that multiple things are missing (in both English and Norwegian). Like "Decide how your Action is invoked" under "Quick setup".
I click on the link, which brings me to settings:
There I can "Edit main invocation handling", which brings med further to the main invocation screen:
As far as I can tell, everything about main invocation is in order, or is it something I'm not seeing here? It also says that there are missing information required for the action directory, among other things for the Norwegian language, that are also present.
PS: Pardon any misspellings, English is not my native language.
UPDATE: As for the English language, it was the name that caused the troubles. "My medicines" contained "My", that apparently don't count, which then caused the name to result to "Medicines", and it's not allowed with single word names. After solving this, I was able to create a release for the English language. But I'm still not sure how to deal with the Norwegian language tho.
UPDATE 2: I ended up just removing Norwegian from the Language settings, and adding it again. Then refilling the mandatory fields and translations. Then it worked!
For the English language, it was the name that caused the troubles. "My medicines" contained "My", that apparently don't count, which then caused the name to result to "Medicines", and it's not allowed with single word names. After solving this, I was able to create a release for the English language.
I was still unable to create a release for the Norwegian language, so I ended up just removing Norwegian from the Language settings, and adding it again. Then refilling the mandatory fields and translations. Then it worked!I was able to create and release in both my languages.
We are a site located in Belgium. We added the 'locale=nl_BE' parameter to our iframe like button so it says like but in the Dutch language (= "vind ik leuk").
This no longer works. When we change the locale to nl_NL (also Dutch language) the like button works again.
When I check the Facebook Internationalization documentation I can't seem to find Belgium or nl_BE, strange right? This worked for months until yeaserday. http://www.facebook.com/translations/FacebookLocales.xml
jsFiddle: http://jsfiddle.net/Jeroenvdb/cw6js/1/
nl_NL (working): https://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.hln.be%3Futm_source%3Dfacebook%26utm_medium%3Dweb&locale=nl_NL&send=false&layout=box_count&width=0&show_faces=false&action=like&colorscheme=light&font&height=85
nl_BE (not working): https://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.hln.be%3Futm_source%3Dfacebook%26utm_medium%3Dweb&locale=nl_BE&send=false&layout=box_count&width=0&show_faces=false&action=like&colorscheme=light&font&height=85
Facebook just closed the bug report I had posted about the nl_BE issue.
"This locale is not currently supported. But you should be able to load the plugin even if a locale is not supported, it will fallback to en_US locale."
http://developers.facebook.com/bugs/442881812429427
That's just plain silly. The change I see compared to a few months ago is that (as is mentioned in the comment on the bug) share buttons no longer break when you pass an unsupported locale but fallback to en_US.
They should get their language/locale act together.
Must be a new bug or code change at Facebook. Similarly, en_EN which worked before no longer works. en_US does work.
I'm trying to add multi language functionality to an existing application.
My URL's look like this:
Without language: www.example.com/controller/action/params
With language: www.example.com/de/controller/action/params
If :lang is not specified ('de' in the example above) it should take the default language (set in the ini) or just use Zend_Translate default keys.
Both of the URL's above need to work.
My Problem now is the following: I'm able to activate get the first URL with the :lang working, but then the default one doesn't work. Why?
Somehow, the chaining of the default route and the language rout doesn't work properly.
My code is the same (for the chaining/routing stuff) like here: http://devzone.zend.com/1765/chaining-language-with-default-route/
I'm not using modules (actively, of course teh default stuff is enabled), maybe my default route (same as in the code) is just wrong? Althought it works, if i disable the language rout and chaining.
I'm using the gwt visualization library to display motion charts in a gwt app. However, the language shown in the chart is random (different language every time it loads).
This:
http://code.google.com/apis/visualization/documentation/using_overview.html#localization
says I can set it, but only through the load method. But the GWT load method does not allow me to set anything other than the version and Packages.
As far as I can tell, there is no way of explicitly setting the language using the GWT API.
Any ideas?
You can set the locale of a GWT application in many ways: Locales in GWT. My guess would be that the Visualization API uses that value to set its own locale value.
You should be able to do a quick test of this by appending locale=fr (change to your desired locale) to the address:
http://www.example.com/MyGwtApp.html?locale=fr
This will force that locale to be used by GWT.
Update: the AjaxLoader does support setting the language via the AjaxLoader.AjaxLoaderOptions:
AjaxLoaderOptions options = AjaxLoaderOptions.newInstance();
options.setLanguage("fr");
AjaxLoader.loadApi("visualization", "1", null, options);
I'm not sure you can use null for the callback parameter, but you get the general idea.
I've discovered that this is a bug, which I've submitted here:
http://code.google.com/p/gwt-google-apis/issues/detail?id=358