15 results found
-
Incorrect Norwegian translations in CMS12 for table settings
As a CMS editor, I want help texts and labels in CMS12 to use correct Norwegian translations, so that I can work efficiently without confusion caused by misleading terms.
In CMS12, the checkbox for adding a table heading is labelled “Vis bildetekst” (Show image caption), which is incorrect. It should refer to “Tittel” (Title), as in previous versions. The best help text here would be “Vis tabelloverskrift” (Show table heading)
The term “bordbredde” is used for table borders. It is not a valid term in this context; it should be “ramme” or "rammebredde".
The root cause seems to be that…
1 vote -
Language Manager won't let you exclude terms, translates Block Names
As a Content Manager, I want to be able to translate pages with an exclusion list which prevents specific words and terms (e.g. Brand Names, Product Names) in content, and Block/Image/Object Names (i.e. Internal Objects which need to be in my native language to administer) from being translated.
Currently, the add-on translates key terms and names and the content manager needs to identify these and translate them back again, but these changes are subsequently lost if the content is re-translated. By managing these globally through a dictionary (or a setting, for Block Names, etc), this would massively improve the admin…4 votes -
Option to exclude properties from translation in Language Manager
As an editor using the Language Manager add-on to translate from one master language to another, I'd like to select individual properties to EXCLUDE from translation. Certain properties (e.g. URL, title etc) may contain key terms, names etc that should not be translated.
Note: This is slightly different from another feedback idea;
https://feedback.optimizely.com/forums/966081-cms-paas-content-management-system/suggestions/49891608-language-manager-won-t-let-you-exclude-terms-tranthough both these ideas would solve the same core problem.
1 vote -
Language Manager Role wise access
In the Languages gadget (Language Manager add-on), users have the option to duplicate content when creating a new language branch. During this process, the “Duplicate content” dialog presents checkboxes for:
Add all children
Add related content(s)
These options are useful for administrators but pose a risk when used by editors who may not fully understand the implications. For example, an editor in our organization mistakenly duplicated a section with over 800 nodes, resulting in around 500 duplicated blocks. This caused significant manual cleanup and unnecessary content clutter.
Feature Request:
We would like the ability to restrict visibility or access to…
2 votes -
Language Manager in combination with the auto translate feature
Language Manager in combination with the auto translate feature
2 votes -
Auto-translate
I use Auto-Transalte a lot but I don't want the Name, URL and Reference to be translated automatically.
When handling multiple language websites it is practical to keep the Name, URL & Reference in English.
The URL I can change manually if necessary
3 votesThank you for raising this feedback request. We will continue to gather feedback to assess demand for this functionality.
-
1 vote
-
[Language Manager] Improve the warning message to make it more meaningful
When translating the pages, you might get the following error:
"Error occurs while translating content, please check the logs for more details."Reason:
In most of cases, the issue happens when the page contains a block that was not enabled for the target language.
For an example: when translating a page from EN -> SV. The page contains a block in ContenArea. The issue happens when the 'sv' language is not enabled for the block.Solution:
As the above example, please enable 'Sv' language for the block.I think we need add more information to the message to make it…
1 vote -
Hreflang Tags
Auto-include hreflang tags in the existing CMS page.
For example, when translating a page from English to French, the system (the Languages gadget) auto-generates an hreflang between the two pages. That is, the English page has an hreflang to the French page and vice versa. We would also like the system to auto-generate self-referencing hreflangs for each page (i.e., English page to itself and French page to itself).
1 vote -
Make Language Manager smarter - extend translate API with IContent and Property
The Translate Interface in language manager add-on (EPiServer.Labs.LanguageManager, to make translations smarter, It would be benificial to add IContent and propertyName. With that, we can get Custom Property Attributes, or other properties to understand better the context.
Change from
TranslateTextResult Translate(
string inputText,
string fromLang,
string toLang;
to
TranslateTextResult Translate(
string inputText,
CultureInfo fromLang,
CultureInfo toLang,
IContent currentContent, //or similar ContentReference
string propertyName
;
With this, we could make the translations smarter by knowing the context of the block or page. We could also read any custom attribute on the property if any.9 votes -
When duplicating content for new language need to add draft content along with published content
We need capability when we are creating content for a new language version for a page, from master language draft content also along with published content should be available, Currently only either published language version or draft version can be added but not both.
We are using EPiServer.Labs.LanguageManager add on to create new language content.
Can this add on EPiServer.Labs.LanguageManager be extended to provide this option.
1 vote -
Translate content items into multiple languages at once
As a marketer, I would like to translate content (pages, blocks, etc. into several languages at the same time, and therefore in just one step.
1 vote -
Translating Inline Blocks
Some of our clients use Inline blocks only and it would be nice if the Language translation gadget would be capable of also providing translation files for these blocks.
1 vote -
Translation of List<T> and LinkCollection item in page is not supported on netframework version (CMS 11
For stringlist and linkitemcollection properties, we could see the values are just duplicated and not translated to native text during the auto translate of page.
The issue is reproducible in Alloy solution and attached the evidence for the same.
Also, please find the attached email from Optimizely team as well.3 votes -
Extend Language Manager Add On - Add/Support new languages
Hi Team
As a Customer, we want to be able to add new languages which are not currently visible or supported in EPiServer Language Manager, so that we can support our current business model as part of our long term strategic plans to migrate our current websites over to the Optimizely CMS/DXP Platform.
Currently within EPiServer CMS, we can only assign one locale per root folder per site in Optimizely which is not really a feasible thing to do. A couple examples of language cultures which are currently not supported within EPiServer Language Manager are : en-fr / en-es and…7 votes
- Don't see your idea?