Skip to content

CMS PaaS (Content Management System)

CMS PaaS (Content Management System)

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

5 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?