Thanks a lot for the information about strings translation and about the hover context information (I examined the POEditor interface and functions quite thoroughly, but this one I have missed). However, and any hints and additional information or explanation in a future will always be welcomed ;-)
However, I have one more question: In POEditor, I miss the suggestions function based on previously translated terms. Such a function is available in Launchpad and it is quite useful and helps a lot to limit duplication and inconsistencies. There is a similar function “Translation memory suggestions” in POEditor, see https://poeditor.com/help/how_to_use_translation_memory. However, this function is not available by default. Is there a chance to make this function available for the Evergreen Project? Eva --- Mgr. Eva Cerniňáková [email protected] Tel. +420 211 222 409 Knihovna Jabok http:/knihovna.jabok.cz Tel. +420 211 222 410 Jabok - Vyšší odborná škola sociálně pedagogická a teologická Salmovská 8, 120 00 Praha 2 po 9. 3. 2020 v 17:03 odesílatel Bill Erickson <[email protected]> napsal: > Hi Eva, > > On Mon, Mar 9, 2020 at 6:00 AM Cerninakova Eva <[email protected]> wrote: > >> Hi Bill, >> >> I have two questions about Angular translations >> >> 1) Would it be possible to provide some feedback like comments or >> explanation to strings containing variables or part of code (preferably >> right in Poeditor) which part of the string to translate and which not. >> It seems obvious , that the parts in quotation marks should not be >> translated, but in some cases I guess it applies not only to the parts >> enclosed in quotation marks. >> E. g. in the string: >> *Error generating print content for template name="<ph >> name="INTERPOLATION"><ex>{{**name}}</ex>{{name}}</ph>" / id="<ph >> name="INTERPOLATION_1"><ex>{{**id}}</ex>{{id}}</ph>" * >> I suppose the >> *name=* >> is part of the code too and only the >> *Error generating print content for template* >> should be translated (but I would like to be sure about it ;-) ) >> >> > It should be safe to ignore any text wrapped in XML elements, specifically > the <ph /> elements. In this example, the following text chunks are meant > to be translated: > > [ Error generating print content for template name=" ] > [ " / id=" ] > [ " ] -- after the last </ph> > > The name= bit does look like code here, but it's just part of the display > message. > > -b > > >
