Open aviavia opened 7 years ago
Hi @aviavia, can you provide some more info? If you set
msgfmt.init('en', {
extractLogLevel: 'trace'
});
are there any clues as to what's going wrong? (for those files / keys)
My best guess without knowing more is that the regex isn't matching on those keys... so if the logs don't provide anything helpful, can you give some examples of what's not being picked up? (e.g. your {{mf ...}}
(are you using this in Blaze?) which may have uncommon use of newlines, etc.
Hi, i don't see anything in the log. I use Blaze. i have a template whit those keys: {{mf 'userSettings' 'Settings'}} {{mf 'userFullName' 'Your full name'}} {{mf 'userSettingsEmail' 'Email'}} {{mf 'phone' 'Phone'}} {{mf 'savedAddress' 'Saved Address'}} {{mf 'myWallet' 'My wallet'}} {{mf 'settingsChangePassword' 'Change Password'}} {{mf 'interestedInStatusNotifications' 'Interested in Status Notifications'}} {{mf 'settingsSave' 'Save'}} {{mf 'settingslogOut' 'Log Out'}} {{mf 'settingsDeleteAccount' 'Delete Account'}} and a few more and {{mf 'userFullName' 'Your full name'}} {{mf 'userSettingsEmail' 'Email'}} are not on the list to translate. maybe because i am using the same default value ('email','Your full name') on other keys? Or maybe because i added them later? cache issue? Thanks.
No, that's ok...
Can you paste the full trace log output?
What version of msgfmt:extract are you using?
Sorry, I missed your reply, how and where do I see the trace log? by the way, i do see all the keys in the DB itself...
msgfmt:core 2.0.0-preview.18 MessageFormat support, the Meteor way msgfmt:extract 2.0.0-preview.12 Extracts native / translatable strings from your app msgfmt:ui 2.0.0 web-based translation UI, optional crowd-sourcing
Is that a problem? { "_id": "r6c8S9XcjKzynnfs9", "lang": "he", "key": "companyRegNumber", "text": "מס' ח.פ./ ע.מ. :", "ctime": 1470595692521, "userId": "jHYSb6ptkKoGP3yQ3", "sourceId": "pFoDTqnhefJ5zaBJw" }
Hi, There are quite many keys to translate which are not appearing on the list to translate.