TYPO3 10: tx_news does not fallback to right language - typo3-10.x

I have the same problem, as: tx_news does not fallback to right language.
I've written a new question, because of different TYPO3 version
Typo3 10.4.25, tx_news: 8.6.0
Default language: DE
Additional languages: EN, FR.
Fallback in FR to EN, if no translation present
Everything works as expected, except tx_news.
tx_news shows DE in FR and not EN as expected.
Any hints?

Related

uwp localization with 1 resource file for all variants of a language

I know how localization in uwp works and I currently have en-US and es-es Resouce files.
What I want to ask is can I just use 1 resource file i.e en and will that affect all variants of English language? like en-us , en-as and all others? and then 1 file for Spanish i.e : es and so on.
all language variants have only few differences between them which are negligible almost in my app. I noticed my app has most of its users from Spain and US only. I assume that is because I am only supporting these 2 languages right now. So I want to support all variants of Spanish and all variants of English but only with 2 files, would that work or do I need to provide 1 file for each variant?
Try checking first if the current app language is any english variant (en-US, en-AS, ...) and if it's true then override it with the one you want.
If ( CurretLanguage == "en-US" || CurrentLanguage == "en-AS" || ...)
{
Windows.Globalization.ApplicationLanguages.PrimaryLanguageOverride = "en-US";
}
Yes, you can do it with single file by just using short language name. In your case, it should be Resources.en.resx for english and Resources.es.resx for spanish. You can refer here for language tags.

Bing Spell Check API works only in English

Trying Bing Spell Check API, but it doesn't seem to work correctly with languages other than English. Available languages for Spell Check
I've tried to check French text, but the results will actually suggest mistakes to a perfectly fine text and vice versa (meaning it also won't correct a mistake in a text).
I've tried checking this text:
La Terre a un noyau interne solide
This is how I've passed the language:
var result = client.SpellCheckerWithHttpMessagesAsync(text: text, mode: "spell", acceptLanguage: "fr-FR").Result;
I've also tried setLang:
var result = client.SpellCheckerWithHttpMessagesAsync(text: text, mode: "spell", setLang: "fr-FR").Result;
The result suggested changing solide to solid which is wrong.
I've tried other texts as well as different languages with the same results.
Am I missing something in how to use this API?
Pls use market parameter mkt=fr-fr in the query and drop the setLang parameter.

PDFKit broken when using Noto Sans font

I'm trying to generate a pdf with Node.js using PDFKit. The pdf contains text in multiple languages, including arabic and russian, so I'm trying to use Noto Sans from Google, but as soon as I use that font, the layout is totally broken, not showing even latin characters:
var doc = new PDFDocument();
doc.registerFont('NotoSans', 'fonts/NotoSans-Regular.ttf');
doc.font('NotoSans');
doc.pipe(res);
doc.fontSize(15);
doc.text('UTF-8 Test');
doc.text('صباح الخیر');
doc.text('japanese');
doc.text('武大郎');
doc.text('RUSSIAN');
doc.text('Привет / здравствуйте');
doc.end();
But this is the result. I expected japanese not to work, but nothing gets displayed correctly. This is the output I get:
Using specific fonts for japanese and arabic works rendering that language, but I need a font that support multiple languages because I'm printing a dynamic table and I don't even know which languages are needed.
You're problem is that NotoSans-Regular.ttf doesn't have all the characters you're looking for. It only has Cyrillic, Greek, Latin characters:
Afrikaans, Aghem, Akan, Albanian, Asu, Azerbaijani, Bafia, Bambara,
Basaa, Basque, Belarusian, Bemba, Bena, Bosnian, Breton, Bulgarian,
Catalan, Central Atlas Tamazight, Chiga, Colognian, Cornish, Croatian,
Czech, Danish, Duala, Dutch, Embu, English, Esperanto, Estonian, Ewe,
Ewondo, Faroese, Filipino, Finnish, French, Friulian, Fulah, Galician,
Ganda, German, Greek, Gusii, Hausa, Hawaiian, Hungarian, Icelandic,
Igbo, Indonesian, Irish, Italian, Jola-Fonyi, Kabuverdianu, Kabyle,
Kalaallisut, Kalenjin, Kamba, Kazakh, Kikuyu, Kinyarwanda, Koyra
Chiini, Koyraboro Senni, Kwasio, Kyrgyz, Langi, Latvian, Lingala,
Lithuanian, Luba-Katanga, Luo, Luyia, Macedonian, Machame,
Makhuwa-Meetto, Makonde, Malagasy, Malay, Maltese, Manx, Masai, Meru,
Mongolian, Morisyen, Mundang, Nama, North Ndebele, Northern Sami,
Norwegian Bokmål, Norwegian Nynorsk, Nuer, Nyankole, Oromo, Polish,
Portuguese, Romanian, Rombo, Rundi, Russian, Rwa, Sakha, Samburu,
Sango, Sangu, Sena, Serbian, Shambala, Shona, Slovak, Slovenian, Soga,
Somali, Spanish, Swahili, Swedish, Swiss German, Taita, Tajik,
Tasawaq, Teso, Tongan, Turkish, Ukrainian, Uzbek, Vietnamese, Vunjo,
Walser, Welsh, Yangben, Yoruba, Zarma, Zulu
You need to load Noto-San in all the languages you're using.
Clone the nato into your project directory:
git clone git#github.com:googlei18n/noto-fonts.git
If you need Korean, Japanese, or Chinese clone these fonts as well:
git clone git#github.com:googlei18n/noto-cjk.git
Now that you have the fonts you want to use you need to register them
// Default
doc.registerFont('NotoSans', 'noto-ckj/hinted/Noto-Regular.ttf');
// Ariabic
doc.registerFont('NotoSansAR', 'noto-ckj/hinted/NotoKufiArabic-Regular.ttf');
// Chines, Korean, Japanese
doc.registerFont('NotoSansCKJ', 'noto-ckj/NotoSansCJK-Regular.ttc');
Once you've got the appropriate font's loaded then you can use them like so:
doc.font('NotoSans');
doc.text('English');
doc.font('NotoSansAR');
doc.text('العربية'); // Arabic
doc.font('NotoSansCKJ');
doc.text('日本語'); // Japanese
doc.text('武大郎'); // Chinese
doc.text('한국어'); // Korean
doc.font('NotoSans');
doc.text('русский'); // Russian
doc.text('ελληνικά'); // Greek
Be careful that you're not loading too many fonts into your PDF since they'll add to the overall size of you document. You may consider using a library like Franc to figure out which fonts you need before loading them.

TYPO3: Show language names for default language in speaking URL using RealURL

I set up a TYPO3 website using TYPO3 4.7. The website is bilingual (German/English) and the are 'speaking' using RealURL.
The default language is German.
So far it works nicely. I get URLs like:
http://www.mywebsite.something/neuigkeiten
http://www.mywebsite.something/kontakt
If the user changes the language to English, he gets URLs like:
http://www.mywebsite.something/en/news
http://www.mywebsite.something/en/contact
If the changes the language back to German, he gets URLs like:
http://www.mywebsite.something/de/neuigkeiten
http://www.mywebsite.something/de/kontakt
The problem is: This creates duplicates for search engines. So, I would like the default language also to use the language parameter for German 'de' as a default in the URLs before the user changes the language.
Does anyone had the same problem before?
Thank you, Chris
Try not to define dafault language in realurl config.
Smth like this should be enough:
array(
'GETvar' => 'L',
'valueMap' => array(
'en' => '1',
),
'noMatch' => 'bypass',
)

yii does not translate korean language

In database, I set language code of Korean - 'ko', but when yii print errors, these errors is english default like this: 이메일 cannot be blank..
Semilar with Maori...
So, what exactly language code of these languages?
And where I can see list of language codes which supported by Yii?
Thanks...