Rozdíly

Zde můžete vidět rozdíly mezi vybranou verzí a aktuální verzí dané stránky.

--- skoda-ep:skoda-storyboard:related-content-translation [31.05.2021 08:56]
Lukáš Čech [Missing content gets localized]
+++ skoda-ep:skoda-storyboard:related-content-translation [31.05.2021 09:17] (aktuální)
Lukáš Čech [Caveats]
@@ Řádek 22: / Řádek 22: @@
 SECONDARY localizations will stay IN SYNC with MASTER, unless manually adjusted (something is added that is missing in MASTER localization or something is removed that is present in MASTER localization). When manually adjusted, relation to the selected content will be marked as **customized**. Below is a table of use-case scenarios to better understand how this process works. Even if some connections are customized, the rest of the connections will try to stay IN SYNC; however the customized connections will never synchronize again.
-==== Missing content gets localized and connected automatically ====
+==== Content gets localized - connects automatically ====
-Once one of the related posts is translated and becomes available in that localization, it will be automatically added to the related content. This is true for both MASTER and SECONDARY localizations.
+Once one of the related posts is translated and becomes available in that localization, it will be automatically added to the related content of other articles that reference its origin translation. This is true for both MASTER and SECONDARY localizations. Refer to the tables below to better understand this process. In short: if you create a 3 new articles in english, connect them together and then translate these articles to czech/slovak etc., all the articles will be connected between each other (unless you manually disconnect them).
@@ Řádek 48: / Řádek 48: @@
 ==== New connection is added in MASTER localization ====
-Article EN-1 is newly connected to 2 more articles: Article EN-5 and Article EN-6. Article EN-6 has existing localization in Serbian language as Article SR-6.
+Article EN-1 is newly connected to 2 more articles: Article EN-5 and Article EN-6. Article EN-6 has existing localization in Serbian language as Article SR-6; however Article EN-5 has no translation in Serbian.
 Status:
@@ Řádek 72: / Řádek 72: @@
 ==== Connected article is translated in SECONDARY localization ====
-Serbian localization decides to translate Article EN-2 as Article SR-2
+Serbian localization decides to translate Article EN-2 as Article SR-2. It is automatically connected from Article SR-1.
 Status:
@@ Řádek 83: / Řádek 83: @@
 ==== New connection is added in SECONDARY localization ====
-Serbian localization creates new Article that only exists in their localization called Article SR-ONLY and add it to connection. They also want to add Article SR-3 back, even though the MASTER language removed it.
+Serbian localization creates new Article that only exists in their localization called Article SR-ONLY and adds it to connection. They also want to add Article SR-3 back, even though the MASTER language removed it.
 Status:
@@ Řádek 94: / Řádek 94: @@
-**IMPORTANT NOTE: Because the Serbian connections now become customized, they are partially disconnected from MASTER localizations. Because Serbian version now added Article SR-3 as their choice, adding or removing Article EN-3 in the MASTER localization will no longer have any effect.**
+**IMPORTANT NOTE: Because the Serbian connections now become customized, they are partially disconnected from MASTER localizations. Because Serbian version now added Article SR-3 as their choice, adding or removing Article EN-3 in the MASTER localization will no longer have any effect on Serbian localization.**
 ==== Existing connection is removed in SECONDARY localization ====
@@ Řádek 110: / Řádek 110: @@
 **IMPORTANT NOTE: Just as with the previous case, where Serbian localization added articles, ARTICLE SR-6 now also becomes customized. This means that any changes in MASTER localization to Article EN-6 will no longer have any effect on Article SR-6.**
+===== Caveats =====
+There are some edge-cases that are not covered by the functionality that include a combination of actions taken by editor that are problematic to solve.
+One of the examples is the following scenario.
+User has a relation defined as follows:
+^  ^ Article English 1 ^ Article Serbian 1 ^ Synchronizing between localizations ^
+^ Connected to | Article English 2 | Article Serbian 2 | ✅ |
+Then removes Serbian article 2:
+^  ^ Article English 1 ^ Article Serbian 1 ^ Synchronizing between localizations ^
+^ Connected to | Article English 2 |  | ❌ |
+Then completely deletes Article Serbian 2 from the administration
+The connection now becomes synchronized again, because the removed post no longer exists:
+^  ^ Article English 1 ^ Article Serbian 1 ^ Synchronizing between localizations ^
+^ Connected to | Article English 2 |  | ✅ |
+Then creates the localization of Article English 2 again:
+^  ^ Article English 1 ^ Article Serbian 1 ^ Synchronizing between localizations ^
+^ Connected to | Article English 2 | Article Serbian 2 | ✅ |