Re: [Django] #19270: makemessages and compilemessages force the location of PO files

[Django]

#19270: makemessages and compilemessages force the location of PO files
-+-
 Reporter:  julen|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (Management |   Resolution:  needsinfo
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  gettext, l10n,   |  Needs documentation:  0
  i18n, makemessages,|  Patch needs improvement:  0
  compilemessages|UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 Any updates or opinions on this?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19270: makemessages and compilemessages force the location of PO files

[Django]

#19270: makemessages and compilemessages force the location of PO files
-+-
 Reporter:  julen|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (Management |   Resolution:  needsinfo
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  gettext, l10n,   |  Needs documentation:  0
  i18n, makemessages,|  Patch needs improvement:  0
  compilemessages|UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by julen):

 I see this is a matter of source vs build locations. You can opt to do the
 same in the docs for example and mix the generated HTML files with the
 source rst files. It'll work, sure, but I doubt you'd want to keep
 everything mixed (independently of thinking if that was the situation
 before or not).

 My suggestion is:
 - ''//.po'' should be used for source
 files
 - ''//LC_MESSAGES/.mo'' or
 ''//LC_MESSAGES/.mo'' should be used for
 generated files. The later is useful for apps that want to install files
 to other directories as part of a setup process when distributing.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19270: makemessages and compilemessages force the location of PO files

[Django]

#19270: makemessages and compilemessages force the location of PO files
-+-
 Reporter:  julen|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (Management |   Resolution:  needsinfo
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  gettext, l10n,   |  Needs documentation:  0
  i18n, makemessages,|  Patch needs improvement:  0
  compilemessages|UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by anonymous):

 It has been working.  Not because it was a good choice, but because nobody
 really has had any choice but to put their PO files in LC_MESSAGES.
 They've prioritised a working Django app over fixing this brokenness.  I
 think everyone who first localises a Django app has to work through this
 confusion, hard to count those lost cycles but they exist.

 So 'working' in this sense isn't a good argument, 'work around' is
 probably a better reason as to why it has been working.

 My personal suggestion would be '$project/po/$lang' for the location of
 the PO files.  But I think the reporter is asking for it to be
 configurable thus:

 makemessage --po-location=myapp/po

 and

 compilemessages --po-location=myapp/po

 The --mo-location could also be configurable making it easier for Django
 apps that are being distributed being placed in the correct place on the
 server.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19270: makemessages and compilemessages force the location of PO files

[Django]

#19270: makemessages and compilemessages force the location of PO files
-+-
 Reporter:  julen|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Core (Management |   Resolution:  needsinfo
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:  gettext, l10n,   |  Needs documentation:  0
  i18n, makemessages,|  Patch needs improvement:  0
  compilemessages|UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => needsinfo
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Indeed, `LC_MESSAGES/` isn't designed to hold PO files. But it's been
 working well until now!

 What layout would you suggest?  What's the value in making the location
 configurable?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19270: makemessages and compilemessages force the location of PO files

[Django]

#19270: makemessages and compilemessages force the location of PO files
-+-
 Reporter:  julen|  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:
Component:  Core (Management |   Keywords:  gettext, l10n, i18n,
  commands)  |  makemessages, compilemessages
 Severity:  Normal   |  Has patch:  0
 Triage Stage:  Unreviewed   |  UI/UX:  0
Easy pickings:  0|
-+-
 Django's `makemessages` and `compilemessages` management commands
 currently force applications to put their PO files under
 LC_MESSAGES/.po//.

 According to the [https://www.gnu.org/software/gettext/manual/gettext.html
 #Locating-Catalogs GNU gettext manual], //LC_// should be used
 for Message Catalog files, i.e. MO files.

 Thus, the cited management commands should //at least// provide an option
 to specify the location of PO files. Ideally PO files should be moved off
 the //LC_MESSAGES// directory too, as it becomes redundant.
 //LC_MESSAGES// directories would only be generated after invoking
 `compilemessages` and would only be used at run-time, as a location where
 compiled files are read from.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.