I've been developing a Smart Home Action which uses Toggles Trait. Everything works fine in English but when I try to execute "turn off" commands in Spanish (customers' predominant language) the Assistant doesn't seem to understand them. It only happens with turn off (desactivar/apagar) commands. Moreover, Spanish syntax that works for triggering the QUERY intent is not correct as any user would talk like that.
Here's a list of EXECUTE command examples in both languages with their result:
Turn on <toggle_name> on <device_name> (english) --> OK
Enciende <toggle_name> en <device_name> (spanish) --> OK
Activate <toggle_name> on <device_name> (english) --> OK
Activa <toggle_name> en <device_name> (spanish) --> OK
Turn off <toggle_name> on <device_name> (english) --> OK
Apaga <toggle_name> en <device_name> (spanish) --> FAIL "Sorry, I don't understand you"
Apaga <toggle_name> on <device_name> (spanish) --> OK "Spanish syntax error. "on" is an English preposition, for Spanish we use "en".
Deactivate <toggle_name> on <device_name> (english) --> OK
Desactiva <toggle_name> en <device_name> (spanish) --> FAIL "Sorry, I don't understand you"
Desactiva <toggle_name> on <device_name> (spanish) --> OK But this is a Spanish syntax error. "on" is an English preposition, in Spanish we use "en".
Here's a list of QUERY command examples in both languages with their result:
Is <device_name> <toggle_name> on? (english) --> OK
Está la opción <toggle_name> encendido en el/la <device_name>? (spanish) --> FAIL
Está el modo <toggle_name> encendido en el/la <device_name>? (spanish) --> FAIL
<toggle_name> la <device_room> está encendido? (spanish) --> OK But horrible syntax, not natural.
<toggle_name> la <device_name> está encendido? (spanish) --> FAIL Althouh is similar to previous syntax.
Is <device_name> <toggle_name> off? (english) --> OK
Está la opción <toggle_name> encendido en el/la <device_name>? (spanish) --> FAIL
Está el modo <toggle_name> encendido en el/la <device_name>? (spanish) --> FAIL
<toggle_name> la <device_room> está apagado? (spanish) --> FAIL Althouh is the horrible syntax that previously worked.
Here's an example of SYNC intent code for adding toggle trait:
availableToggles: [
{
name: "photocaller_toggle",
name_values: [
{
name_synonym: [
"Photocaller",
"photo caller",
"photocall",
"Auto foto",
"fotos",
"foto automática"
],
"lang": "es"
},
{
name_synonym: [
"Photocaller",
"photo caller",
"photocall",
"photos",
"auto photo",
"automatic photo"
],
lang: "en"
}
]
},
],
commandOnlyToggles: false,
queryOnlyToggles: false,
Is there a possible solution to fix this? Or anyway to tell Google so they are aware of it?
Please file this information through the public bug tracker.
Related
I am trying to get the translation to work in Typo3 12.1.3.
I build a simple site package following the Sitepackage Tutorial.
I added some locallang files:
locallang.xlf
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" datatype="plaintext" original="EXT:site_package/Resources/Private/Language/locallang.xlf" date="2011-10-17T20:22:32Z" product-name="site_package">
<header/>
<body>
<trans-unit id="test" resname="test">
<source>Test (EN)</source>
</trans-unit>
</body>
</file>
</xliff>
de.locallang.xlf
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" target-language="de" datatype="plaintext" original="EXT:site_package/Resources/Private/Language/locallang.xlf" date="2011-10-17T20:22:32Z" product-name="site_package" >
<header/>
<body>
<trans-unit id="test" resname="test" approved="yes">
<source>Test (EN)</source>
<target>Test (DE)</target>
</trans-unit>
</body>
</file>
</xliff>
Created some template:
<f:layout name="Default" />
<f:section name="Main">
<main role="main">
<div class="container">
<div class="row">
<div class="col-md-12">
<f:translate key="LLL:EXT:site_package/Resources/Private/Language/locallang.xlf:test"/>
<f:translate key="test" extensionName="site_package"/>
<f:for each="{mainContent}" as="contentElement">
<f:cObject
typoscriptObjectPath="tt_content.{contentElement.data.CType}"
data="{contentElement.data}"
table="tt_content"
/>
</f:for>
</div>
</div>
</div>
</main>
</f:section>
And added a site configuration:
base: /
languages:
-
title: English
enabled: true
languageId: 0
base: /
typo3Language: default
locale: en_US.UTF-8
iso-639-1: en
navigationTitle: English
hreflang: en-us
direction: ltr
flag: us
websiteTitle: ''
-
title: Deutsch
enabled: true
base: /de/
typo3Language: de
locale: de_DE
iso-639-1: de
websiteTitle: ''
navigationTitle: Deutsch
hreflang: de-DE
direction: ''
fallbackType: strict
fallbacks: '0'
flag: de
languageId: 1
rootPageId: 1
websiteTitle: ''
Afterwards I created a site, added some content and translated it to German in the backend.
Problem:
The content elements are presented in the selected language in the frontend.
If I switch it, they are presented in the matching language.
The text from the locallang file stays in the default language.
If I switch the language, they are not presented in the right language. They stay in English.
What am I doning wrong?
Thanks a lot for your help!
can you check again with TYPO3 v12.2.0? This might solve these problems...
I have the same issue with TYPO3 v12.2 like the threadstarter. I'm using DDEV locally and the main content of the page is German and created a page translation to English. The output still remains in English.
The section for languages in the config.yaml file in my site configuration:
languages:
-
title: Deutsch
enabled: true
base: /
typo3Language: de
locale: de_DE.utf8
iso-639-1: de
websiteTitle: 'Meine Webseite'
navigationTitle: Deutsch
hreflang: de-DE
direction: ''
flag: de
languageId: 0
-
title: English
enabled: true
base: /en/
typo3Language: default
locale: en_US.utf8
iso-639-1: en
websiteTitle: 'My website'
navigationTitle: English
hreflang: en-US
direction: ''
fallbackType: fallback
fallbacks: '0'
flag: en-us-gb
languageId: 1
The German translation file de.locallang.xlf looks like this:
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" datatype="plaintext" original="EXT:custompackage/Resources/Private/Language/locallang.xlf" date="2020-10-18T18:20:51Z" product-name="custompackage" target-language="de">
<header/>
<body>
<!-- Topbar -->
<trans-unit id="topbar.book-appointment" resName="topbar.book-appointment" approved="yes">
<target state="translated">Termin online buchen</target>
</trans-unit>
</body>
</file>
</xliff>
The English (default) translation file locallang.xlf looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file source-language="en" datatype="plaintext" original="EXT:custompackage/Resources/Private/Language/locallang.xlf" date="2020-10-18T18:20:51Z" product-name="custompackage">
<header/>
<body>
<!-- Topbar -->
<trans-unit id="topbar.book-appointment">
<source>Book appointment</source>
</trans-unit>
</body>
</file>
</xliff>
Fluid template, first with German default label, second without:
<f:translate extensionName="custompackage" id="topbar.book-appointment">Termin online buchen</f:translate>
<f:translate extensionName="custompackage" id="topbar.book-appointment"/>
The second variant returns the English label by default.
I also noticed changing the user backend language affects the frontend localization output. If German was set up as a user backend language, German labels appear in the frontend and with English the other way. That's a strange behavior. Any idea why this happens?
What's the right way to set up translations for own composer extensions?
Do they belong to var/labels/{language}/{customExtension} or the regular way to packages/{customExtension}/Resources/Private/Language/locallang.xlf? The localization documentation for TYPO3 v12 (main) shows the regular way.
I have the same problems like you both with TYPO3 12.2.0.
But I've made a mistake with my folder name. I created a folder named "Languages", but it has to be "Language".
So maybe check your convensions ... now the Localisation works fine with TYPO3 12. You don't need a second Website Language to show your data in different languages. You only need special files, like locallang.xlf for english and de.locallang.xlf for german.
I make an app with blazor wasm in VSCode.
When I build my app I add the error below :
error CS0246: Le nom de type ou d'espace de noms 'MainLayout' est introuvable (vous manque-t-il une directive using ou une référence d'assembly ?) [...source\repos\WebApp3\Client\WebApp3.Client.csproj]
In program.cs the App.razor is not recognized :
enter image description here
The problem is probably due to the settings in the .csproj file.
Have you an idea ?
I have read all documentation and something that seems obvious is not happening in my installation. I have several domains:
domain.net
domain.fr
domain.it
all of them are pointing the typo3 folder in server. After adding all these domains and corresponding languages in site management > sites
I still only get original frontend in .net domain rest wont show anything (blank).
Note: most information online is older versions and it seems that this point has been simplified in this version, so there is no need to include any code in .htaccess or other files. Also followed this
Looking into my folder tree I can see these folders (for each site) in mainfolder/typo3conf/sites and every of them has its config.yaml file.
Substituted real name for "domain"
this is what .net looks like (english version)
base: 'https://example.net/'
baseVariants: { }
errorHandling: { }
languages:
-
title: English
enabled: true
base: 'https://example.net/'
typo3Language: default
locale: en_US.UTF-8
iso-639-1: en
websiteTitle: ''
navigationTitle: English
hreflang: en-US
direction: ltr
flag: en-us-gb
languageId: '0'
rootPageId: 1
routes: { }
websiteTitle: ''
This is .fr (french version)
base: 'http://example.fr/'
baseVariants: { }
errorHandling: { }
languages:
-
title: French
enabled: true
languageId: '0'
base: 'http://example.fr/'
typo3Language: fr
locale: fr_FR.UTF-8
iso-639-1: fr
navigationTitle: Français
hreflang: fr-fr
direction: ltr
flag: fr
websiteTitle: ''
rootPageId: 2
routes: { }
websiteTitle: ''
Tree inside is just this
Pages have dummy content we arent developing anymore until this problem is solved.
Any idea?
Server setup should be ok as before typo3 i was able to have a wordpress multisite and it did show content. As WP isnt native multilanguage and it works with all kind of plugins that just break everything when you update. This is why we are changing to typo3. But that is another story.
Usually when everything seems fine but it doesnt work, its something silly.
.fr domains and others were handling a lower version of php so it wouldnt run typo3
So if something like this happens to you check php version on every domain!!!
I use CR2013 with SAGE X3 V7. A former coworker created a custom function to format phone numbers. We use this function in a lot of reports. We are migrating Sage X3 to a new version in a new server. Reports have been moved to this new server.
But when we print a report using this function from the new X3 version, we have this error code
Message 1/3 : Erreur à l'ouverture du rapport: xxxxxxxxxx\ZARCCLIENT.rpt
- Message 2/3 : Echec du chargement du rapport
- Message 3/3 : Erreur dans le fichier ZARCCLIENT 6976_2964_{B35860BF-F698-4802-8025-B91607C6EBEF}.rpt :
Erreur dans la formule USR_Tel:
'if ({BPADDRESS_USR.TEL_0} <> "") then ZFormatTelephoneFax ({BPADDRESS_USR.TEL_0}, {TABCOUNTRY_USR.TELFMT_0})
'
L'UFL u212com.dll qui implémente cette fonction est manquante.
I Installed CR2013 on the new server.
I copied the u212com.dll from the old to the new server and I types the following command following this instructions : CrystalReports_QRCode_UFL
gacutil -i CRUFL_u212com.dll
Regasm u212com.dll
but I have these errors codes
Échec de l'ajout de l'assembly au cache : Le module était censé contenir un manifeste de l'assembly.
RegAsm : error RA0000 : Échec de chargement de 'C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\u212com.dll', car ce n'est pas un assembly .NET valide
When I open a crystal report and I go in the formula workshop, I can't see any functions in the report custom function, on the new and on the old server.
I can't access the repository custom function, i have no user and password. And I don't think I have a Central Management Server installed.
When i create a function, in the old server, I can find my custom function in Functions/Additionnals functions/UFL COM and Net (u212.com.dll) if it can help.
So how can I use this custom function on my new server?
How can I see the custom function code in Crystal reports?
Thank you for helping.
Maybe your u212com.dll is not .NET dll, but pure COM one? In that case you have to register it in cmd shell, using regsvr32:
regsvr32 u212com.dll
You need to run command prompt as administrator of course.
I want to add two other modules in my application. but when I try to install the modules Waherouse and purchase management, installation is not possible with this error
"
ValidateError
Une erreur est apparue lors de la validation du/des champ(s) vat: Ce code de TVA ne semble pas correct. Note: le format attendu est 'CC##' (CC=Country Code, ##=VAT Number)
"
The accounting module is already installed and the completed status
I need your help
Thank