Hi Damian,
as I noted after the last release on Feb 23rd (see https://groups.google.com/forum/#!topic/silverstripe-dev/TwHdMTxN5MQ ) the transifex status for German shows 100% but there are several strings not translated, e.g. Boolean.YESANSWER and Boolean.NOANSWER.
https://github.com/silverstripe/silverstripe-framework/blob/3.1/lang/de.yml#L61
https://github.com/silverstripe/silverstripe-framework/blob/3.1/lang/en.yml#L61
But… those YESANSWER and NOANSWER are not on transifex…
How often are the English source files updated? Or don’t they change that often? However, it seems they’re outdated…
Most confusion was (as kingkozzer stated) about the date (August / May) and that I saw “German 100%” but some strings untranslated. Maybe the master upload to transifex is broken, not the sync back?
I just translated the last two untranslated strings for cms, now it should update for at least German ;)
Cheers,
Werner
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
Thanks for that. I've merged the PR and will investigate those other strings tomorrow.
Kind regards
Damian
You received this message because you are subscribed to a topic in the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/silverstripe-dev/PcGki_saaak/unsubscribe.
To unsubscribe from this group and all its topics, send an email to silverstripe-d...@googlegroups.com.
I noticed this today also. Seems not only English master is updated somehow?
Yup, seems to be the changed english phrases in the en.yml causing the existing translatins to disappear.
But… what is worse? We don’t notice a changed phrase (which would not happen when a really new phrase has another key) or re-translating the key (which is copy/paste from the history)
It’s annoying for simple typo fixes, but I guess we’ll have to live with it.
Damian, thanks for researching that issue, now it’s more clear to me.
Cheers,
Werner
Von: dam...@silverstripe.com [mailto:silverst...@googlegroups.com] Im Auftrag von Damian Mooyman
Gesendet: Montag, 16. November 2015 21:41
An: SilverStripe Core Development
In cms we have a strange history sometimes… e.g.
CMSSiteTreeFilter_DeletedPages.Title
Was first “All pages, including archived”,
then it was “…included deleted”,
now it’s “including archived” again…
Did you guys still not decide what phrase to choose or is this some automated update script chaos?
Cheers, Werner
Von: dam...@silverstripe.com [mailto:silverst...@googlegroups.com] Im Auftrag von Damian Mooyman
Gesendet: Montag, 16. November 2015 21:41
An: SilverStripe Core Development