[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    D26584: Load localization catalog for slideshow config window
From:       David Edmundson <noreply () phabricator ! kde ! org>
Date:       2020-01-12 15:59:01
Message-ID: 1fc4074714dca74acbd3cac859dbcfd5 () localhost ! localdomain
[Download RAW message or body]

[Attachment #2 (text/plain)]

davidedmundson added a comment.


  > I'm still not totally clear on why some things require a domain to be added for \
translations, and other things don't.  
  Everything requires a domain set in some way.
  
  For apps/C++ this is done effectively magically at compile time.
  
  For QML we have to have some code somewhere that says "this QML context should use \
this i18n domain", which is all in kdeclarative. This is already quite messy, but the \
real complication is when one context loads a plugin from something else - we haven't \
solved that, so we specify a domain explicitly.

REPOSITORY
  R120 Plasma Workspace

REVISION DETAIL
  https://phabricator.kde.org/D26584

To: yurchor, #plasma, #localization, ngraham
Cc: davidedmundson, ngraham, plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, \
zachus, fbampaloukas, GB_2, ragreen, ZrenBot, alexeymin, himcesjf, lesliezhai, \
ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart


[Attachment #3 (text/html)]

<table><tr><td style="">davidedmundson added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: \
right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: \
#F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: \
inline-block; border: 1px solid rgba(71,87,120,.2);" \
href="https://phabricator.kde.org/D26584">View Revision</a></tr></table><br \
/><div><div><blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; \
font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: \
#f8f9fc;"><p>I&#039;m still not totally clear on why some things require a domain to \
be added for translations, and other things don&#039;t.</p></blockquote>

<p>Everything requires a domain set in some way.</p>

<p>For apps/C++ this is done effectively magically at compile time.</p>

<p>For QML we have to have some code somewhere that says &quot;this QML context \
should use this i18n domain&quot;, which is all in kdeclarative. This is already \
quite messy, but the real complication is when one context loads a plugin from \
something else - we haven&#039;t solved that, so we specify a domain \
explicitly.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R120 \
Plasma Workspace</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a \
href="https://phabricator.kde.org/D26584">https://phabricator.kde.org/D26584</a></div></div><br \
/><div><strong>To: </strong>yurchor, Plasma, Localization, ngraham<br /><strong>Cc: \
</strong>davidedmundson, ngraham, plasma-devel, LeGast00n, The-Feren-OS-Dev, \
jraleigh, zachus, fbampaloukas, GB_2, ragreen, ZrenBot, alexeymin, himcesjf, \
lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart<br \
/></div>



[prev in list] [next in list] [prev in thread] [next in thread]