Conversation
| <trans-unit id="dialogs.uninstall_success.content"> | ||
| <source xml:lang="en">{app_title} was successfully uninstalled.</source> | ||
| <target xml:lang="id">{app_title} berhasil dicopot pemasangannya.</target> | ||
| <target xml:lang="id" state="needs-translation">{app_title} was successfully uninstalled.</target> |
There was a problem hiding this comment.
🚩 Indonesian translation reverted to English in velopack.xlf
The existing Indonesian translation for dialogs.uninstall_success.content was replaced with untranslated English text:
- Before:
<target xml:lang="id">{app_title} berhasil dicopot pemasangannya.</target> - After:
<target xml:lang="id" state="needs-translation">{app_title} was successfully uninstalled.</target>
This is a translation regression — a valid Indonesian localization was replaced with English. The state="needs-translation" attribute was added, which suggests Crowdin intentionally reset this translation (perhaps due to a source string change or translator action). However, it's worth confirming this was intentional and not a Crowdin sync artifact that accidentally lost a valid translation.
Was this helpful? React with 👍 or 👎 to provide feedback.
| <target xml:lang="pt-PT" state="translated">Usando a assinatura da **Comunidade Local** por **{0}**. Expira {1}</target> | ||
| <note>ID: SubscriptionStatus.UsingLocalCommunitySubscription</note> | ||
| </trans-unit> | ||
| <trans-unit id="SubscriptionStatus.UsingEnterpriseSubscription" approved="yes"> | ||
| <trans-unit id="SubscriptionStatus.UsingEnterpriseSubscription"> | ||
| <source xml:lang="en">Using **Enterprise** subscription for {0}. Expires **{1}**</source> | ||
| <target xml:lang="pt-PT" state="final">Usando a assinatura de **Enterprise** para {0}. Expira **{1}**</target> | ||
| <target xml:lang="pt-PT" state="translated">Usando a assinatura de **Enterprise** para **{0}**. Expira **{1}**</target> |
There was a problem hiding this comment.
🚩 Portuguese translations modified bold formatting on placeholders
Two translation entries in pt/Bloom.xlf had their approved="yes" removed and their state changed from final to translated, with the translation text modified to bold-wrap the {0} placeholder:
SubscriptionStatus.UsingLocalCommunitySubscription:por {0}→por **{0}**SubscriptionStatus.UsingEnterpriseSubscription:para {0}→para **{0}**
The English source strings do NOT have **{0}** (only {0}), so the Portuguese translation now adds bold formatting that doesn't exist in the source. This could be an intentional translator choice for emphasis, or it could be an accidental deviation from the source format. Worth verifying this was intentional.
Was this helpful? React with 👍 or 👎 to provide feedback.
| <trans-unit id="dialogs.uninstall_success.content"> | ||
| <source xml:lang="en">{app_title} was successfully uninstalled.</source> | ||
| <target xml:lang="id">{app_title} berhasil dicopot pemasangannya.</target> | ||
| <target xml:lang="id" state="needs-translation">{app_title} was successfully uninstalled.</target> |
There was a problem hiding this comment.
🟡 Indonesian uninstall success translation regressed to English source text
The Indonesian (id) velopack translation for dialogs.uninstall_success.content was replaced from a valid Indonesian translation to the English source text.
Translation Regression Details
The previous translation was:
{app_title} berhasil dicopot pemasangannya.
This was a proper Indonesian translation meaning the app was successfully uninstalled. The new version replaces it with:
{app_title} was successfully uninstalled. with state="needs-translation"
This appears to be a Crowdin sync issue that lost an existing translation. Indonesian users will now see English text for this uninstall success message instead of the previously available Indonesian translation.
Impact: Indonesian users see English instead of their native language for the uninstall success dialog.
| <target xml:lang="id" state="needs-translation">{app_title} was successfully uninstalled.</target> | |
| <target xml:lang="id" state="translated">{app_title} berhasil dicopot pemasangannya.</target> |
Was this helpful? React with 👍 or 👎 to provide feedback.
| <trans-unit id="comic.template.paper.full.bleed" approved="yes"> | ||
| <source xml:lang="en">This template tells Bloom that this book is a candidate for "<g id="genid-2" ctype="x-html-a" html:href="https://dw-wp.com/resources/cartooning-quickguides/layout-quickguides/quickguides-bleeds/">full bleed</g>" printing by a printshop. This feature is available with a Bloom subscription. If this feature is enabled, then in the Edit tab, you will see semi-opaque borders. The outer one is the "bleed"; this is the area that will probably be cut off by a printshop. The inner border is an area that <g id="genid-3" ctype="x-html-em">might</g> be cut off, so you should avoid putting things in there that would look really bad if they were cut off. To actually get a PDF that is ready for this commercial printing, please see the "PDF Options" under the Publish Tab.</source> | ||
| <target xml:lang="fr" state="final">Ce modèle indique à Bloom que ce livre est candidat à l'impression « <g id="genid-2" ctype="x-html-a" html:href="https://dw-wp.com/resources/cartooning-quickguides/layout-quickguides/quickguides-bleeds/">full bleed</g> » par une maison d'edition. Cette fonction n' est disponible qu'avec un abonnement Bloom. Si cette fonction est activée, on verra apparaître, dans l'onglet Édition, des bordures semi-opaques. La bordure extérieure est le « fond perdu » : la zone qui sera probablement coupée lors de l'impression. Puisque la bordure intérieure est une zone qui <g id="genid-3" ctype="x-html-em">pourrait</g> être coupée, il faut éviter d'y placer des éléments qui seraient assez deformés si coupés. Pour obtenir un PDF prêt pour l'impression commerciale, veuillez consulter les « Options PDF » sous l'onglet « Edition ».</target> | ||
| <target xml:lang="fr" state="final">Ce modèle indique à Bloom que ce livre est candidat à l'impression « <g id="genid-2" ctype="x-html-a" html:href= »https://dw-wp.com/resources/cartooning-quickguides/layout-quickguides/quickguides-bleeds/« >full bleed</g> » par une maison d'edition. Cette fonction n' est disponible qu'avec un abonnement Bloom. Si cette fonction est activée, on verra apparaître, dans l'onglet Édition, des bordures semi-opaques. La bordure extérieure est le « fond perdu » : la zone qui sera probablement coupée lors de l'impression. Puisque la bordure intérieure est une zone qui <g id="genid-3" ctype="x-html-em">pourrait</g> être coupée, il faut éviter d'y placer des éléments qui seraient assez deformés si coupés. Pour obtenir un PDF prêt pour l'impression commerciale, veuillez consulter les « Options PDF » sous l'onglet « Edition ».</target> |
There was a problem hiding this comment.
🔴 Corrupted XML href attribute in French translation uses guillemets instead of quotes
In the French translation for comic.template.paper.full.bleed, the html:href attribute value has its double quotes replaced with French guillemets (« and »), producing html:href= »https://...« > instead of html:href="https://...". This corrupts the XML attribute, breaking the hyperlink in the rendered localized content. Compare with the source on line 26 which correctly uses html:href="https://...", and the v2 translation on line 33 which also correctly preserves the quotes.
Was this helpful? React with 👍 or 👎 to provide feedback.
| <trans-unit id="CollectionSettingsDialog.AdvancedTab.Program" translate="no"> | ||
| <source xml:lang="en">Program</source> | ||
| <target xml:lang="ksw" state="needs-translation">Program</target> | ||
| <note>ID: CollectionSettingsDialog.AdvancedTab.Program</note> | ||
| </trans-unit> | ||
| <trans-unit id="CollectionSettingsDialog.AdvancedTab.QrCodes" translate="no"> | ||
| <source xml:lang="en">QR Codes</source> | ||
| <target xml:lang="ksw" state="needs-translation">QR Codes</target> | ||
| <note>ID: CollectionSettingsDialog.AdvancedTab.QrCodes</note> | ||
| </trans-unit> | ||
| <trans-unit id="CollectionSettingsDialog.AdvancedTab.ShowQrCodes" translate="no"> | ||
| <source xml:lang="en">Show QR Codes</source> | ||
| <target xml:lang="ksw" state="needs-translation">Show QR Codes</target> | ||
| <note>ID: CollectionSettingsDialog.AdvancedTab.ShowQrCodes</note> | ||
| </trans-unit> | ||
| <trans-unit id="CollectionSettingsDialog.AdvancedTab.ShowQrCodes.Description" translate="no"> | ||
| <source xml:lang="en">Scanning the code or clicking the badge will take the user to the collection of books in this collection's primary language. Note, if you want to use this but your branding does not show it, contact us.</source> | ||
| <target xml:lang="ksw" state="needs-translation">Scanning the code or clicking the badge will take the user to the collection of books in this collection's primary language. Note, if you want to use this but your branding does not show it, contact us.</target> | ||
| <note>ID: CollectionSettingsDialog.AdvancedTab.ShowQrCodes.Description</note> | ||
| </trans-unit> |
There was a problem hiding this comment.
🚩 Inconsistent QR code translation IDs across locales
The ksw, qaa, and yua locales use a different set of translation IDs for QR code functionality (CollectionSettingsDialog.BookMakingTab.QrCodeBadgeLabelCaption, BookMakingTab.QrCodeBadgeText, BookMakingTab.QrCodeLabel, BookMakingTab.QrCodeShowLanguage) compared to all other ~30 locales which use CollectionSettingsDialog.AdvancedTab.QrCodes, AdvancedTab.ShowQrCodes, AdvancedTab.Caption, AdvancedTab.QrCodeBadgeText, etc. Not only are the IDs different, but the source strings differ too (e.g., "Show QR code for current language books" vs "Show QR Codes"). Neither set of IDs is currently referenced in the src/ source code, suggesting this is for an upcoming feature. When the feature lands, whichever set of IDs is used in code, the other locales will have missing translations. This should be reconciled before the feature goes live.
Was this helpful? React with 👍 or 👎 to provide feedback.
This change is