How would you manage right to left content in aem for Arabic languages using msm; E.g. Search box, the search icon will be on left for Arabic site?
Language specific styling is usually handled applying specific css/js to the content. I have not done Arabic site specifically but have done Chinese or Japanese which are also right to left.
As practice, your site could provide the locale information and based on that locale CSS namespacing can be used to get the specific language styling
Related
In Typo3, is there any way I can disable the language labels next to the content elements?
Or even better: Is there a way to disable all language features for a single-language site? Though the other language options are not that important as I can disable them via Page TSConfig.
It's not possible to disable all language features since even if you only have one language. You need some language specific settings, e.g. locale for date formatting or typo3Language to get the proper translation of labels in the frontend.
Nevertheless, you can change the label next to the flag:
Go to the Sites module on the left side
Select your site configuration
Go to the "Languages" tab
Select your language
Change the title, e.g. to Deutsch
I am using wagtail and my user wishes to be able to change font sizes in the Rich text editor. I have attempted to use TinyMCE but the install is problematic (see this question and non-answer)
Is there an alternative that would provide the functionality that I am looking for?
You'd probably consider this a non-answer too, but if a rich text editor with that feature did exist, it would be breaking the design principles of Wagtail. Wagtail is a system for capturing and presenting information, not a web design package, and mixing the two is liable to lead to all kinds of problems down the line (inconsistent styling between pages, difficulty redesigning or migrating the site in future, accessibility for screen-reader users).
The correct alternative is to find out what information your client wishes to communicate with different font sizes, and then make sure you're modelling that information in your page models. For example, if they want to include pull-quotes in their text, you can model the page content as a StreamField with a pull-quote block type (with its own text style defined by you in HTML/CSS). If they don't have any specific informational purpose in mind, and just want to play around with fonts, then gently advise them that that's your job, not theirs...
I've been building a TYPO3 website. I wanted to use the multi-language capacity of TYPO3 and get acquainted with the CMS. I'm using V.9.5.6 at the moment with the Introduction Package.
I followed the manual on multi-language setup here : https://docs.typo3.org/m/typo3/guide-frontendlocalization/9.5/en-us/Index.html
When switching languages, the page refreshes but no visible changes occur.
I deleted the original "German" et "Dansk" languages, then added "French" and "German". I used the contact page as proving grounds.
I added translations in germand and french from the original english page I built. There's only a header and a contact form. In english, it reads "contact form". In german and french it should read respectively "Kontaktieren Sie uns" and "Contactez-nous".
The languages UIDs are 2 for German and 3 for French. The template, in the languages section, has "auto" for the list of languages and it pulls correctly the 2 I added, in the correct order.
In a properly setup website, if default language is English, and I click on the "German" or "French" language button at the bottom, the page should refresh and display the content translated in the language I selected and have the selected language in bold at the bottom of the page.
When clicking on the bottom links, it adds the correct L= parameter and the page loads but no visible change occur on the page. Even the language link at the bottom of the page has "Default" in bold instead of whatever I clicked.
There is NO error message when clicking on the language buttons.
I'm pretty sure this is not the standard behavior of a TYPO3 multi-lingual installation. What can cause the CMS to not fetch a translated content OR fail to get the language change information from the parameters passed in the URL ?
I'll try to answer this vague question.
Usually there are three pitfalls you should look at:
realurl (or routes in v9) here is a nice gist: https://gist.github.com/koehlersimon/9dcbabb6b1b2adcbc84db96fd144fb08
TypoScript settings for the languages: https://docs.typo3.org/m/typo3/guide-frontendlocalization/9.5/en-us/TyposcriptConfiguration/Index.html#typoscript-configuration
proper .htaccess in connection with [1.]
I also suggest to update to v 9.5.9
There have been plenty bugfixes since v 9.5.6 and updating within branch 9.5.X is really easy and non-breaking!
I need to enable right to left language support in AEM text component. I could google that page should contain <html dir="rtl"....> and I assume there is something that needs to be done on AEM as well.
Any help?
When you have to implement RTL (right-to-left) functionality in your website it is not only the front-end that has to work in a RTL-way. Also the author-interface should work as much as possible RTL, because that is what the author expects.
Page-Template
When designing your page-component your element should contain the “dir”-attribute with the value of rtl.
I would like you to go through these articles:-
Link:- http://blog.globalizationpartners.com/adobe-experience-manager.aspx
//Example to convert content from english to Arabic
Link:- http://blogs.adobe.com/experiencedelivers/experience-management/rtl-adobe-cq5-aem/
// This article tells about how template, RTE, Dialogs need modification.
Link:- https://adobeaemtherightway.wordpress.com/2014/05/02/website-globalization-and-localization-best-practices/
//Specialized Layout Requirements
Languages such as Arabic and Hebrew are read right-to-left (RTL). Often times, layouts and imagery from a site’s master branch are not designed with these special language requirements in mind. For example, text within a background image requires sufficient space in the image to safely incorporate the copy and is usually displayed at one end of the image, as seen below.
Reference Posts:-
http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__ntwc-do_we_have_anybuilt.html
http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__fccj-hi_all_i_havea.html
I hope this would be helpful to you.
Thanks and Regards
Kautuk Sahni
(Adobe AEM Forums)
We need to run a help portal for users of our application. We want every page to be accesible in several languages.
I want to find a content-management system which would have rich translation features, such as:
Per-paragraph translation;
Warnings for translated content that wasn't updated after a change was made to another language;
Possibility to choose whether to show or hide paragraphs/pages which are not translated;
Easy and user-friendly switching between languages (e.g. "this page is accessible in the following other languages: ...").
I found a MediaWiki plugin which allows at least some of the above mentioned. Are there any CMSes with native orientation for translations and multilingual content?
The Daisy CMS has great built-in translation support.
Break your content into sections and translate them individually, or whole pages at a time.
You can run a report that tells you which documents have translations that are out of sync with the base language, and which documents don't have translations at all. You can then translate inside the app or export for offline translation and import later.
You can exclude untranslated pages and paragraphs from the locale-specific navigation automatically.
The menu will automatically show the user which languages are available for a specific page.