That's also what I thought. Which is the reason why I can't see why I cannot extract in one operation every messages that may be displayed by my app: the core messages (like you said, the times/dates stuff), my app messages (from my views, controllers...) and the model validation messages.
I've opened a ticket on lighthouse about my issue: http://cakephp.lighthouseapp.com/projects/42648-cakephp/tickets/3442 Le dimanche 9 décembre 2012 20:01:07 UTC+1, euromark a écrit : > > @cricket > I think you messed sth up earlier. > the dev messages (domain dev) are the ones not public. > the normal core messages will very much end up in the frontend (being > times/dates for examples or other global stuff) > > its just that they do not change that often - compared to the app ones. > > > > > Am Sonntag, 9. Dezember 2012 03:00:02 UTC+1 schrieb cricket: >> >> On Sat, Dec 8, 2012 at 5:10 AM, Cyrille Faucheux >> <[email protected]> wrote: >> > Yes, using version control is a solution, just as saving and replacing >> some >> > files, but I don't like this solution, because it requires a manual >> > intervention. >> > >> > What do you mean by "nothing will get done" ? That "it's working the >> way >> > it's meant to work", or that "nobody will take care of it" ? >> >> I was referring to your unwillingness to overwrite your pot files. But >> I think now that I misunderstood what you meant. When you extract the >> core files you should be asked: "Would you like to merge all domains >> [sic] strings into the default.pot file?" >> >> If you choose not to, you'll end up with several files: >> >> app.pot cake_console.pot cake_dev.pot cake.pot default.pot >> >> The default file is the one with your app's strings. >> >> > I can submit a patch if it's what you are pointing out. I'm just >> looking for >> > some insight about how it's supposed to work. >> >> I don't know what the initial problem is, or whether it's a bug. If >> you think it is you can report it here (or check if it's already >> there): >> >> http://cakephp.lighthouseapp.com/dashboard >> >> > Currently, I can't see why the extract process has an option >> > "--extract-core". Why would someone want to ignore the core messages ? >> And >> > why extracting the core messages is exclusive to extracting the >> validation >> > messages ? Does someone knows why it has been desined this way ? >> >> Many people (myself included) will not want to translate the core >> messages because with debug = 0 they will not be seen by the public. >> If I'm not going to take the time to translate them, I'm not going to >> want them extracted (and certainly not merged into default.pot). The >> exception is for 404 errors and such, but those can be placed in >> View/Error and they'll be extracted along with the rest of the >> non-core files. But missing_action, missing_table, etc. can be ignored >> because those aren't errors that should be thrown in a live site. Of >> course, it's another story if your developers would prefer reading dev >> errors in their own language. But it's good to have the option whether >> to extract everything or just the app's strings because a lot of >> people can't be bothered. >> > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php?hl=en.
