Nicolas Goaziou n.goaz...@gmail.com writes:
+(defconst org-export-dictionary
Why?
Nicolas Goaziou n.goaz...@gmail.com writes:
I would like to move every variable and function related to
internationalization (i.e smart quotes and translations) in a dedicated
file (ox-i18n.el) instead of ox.el.
Considering ox.el is 6k lines long, I think it can be a bit tedious to
locate
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
+(defconst org-export-dictionary
Why?
Because it is not meant to be changed by the user nor let-bound. IOW,
it's a constant.
Regards,
--
Nicolas Goaziou
Hello,
+(defconst org-export-dictionary
Why?
Because it is not meant to be changed by the user nor let-bound. IOW,
it's a constant.
But perhaps it should not be. Consider org-export-smart-quotes-alist.
In Danish, according to the 'official' guidance, all of
Hello,
Rasmus ras...@gmx.us writes:
Should the ox-latex language-code to babel list also be included in an
ox-int'l file? The reason is that I found some bugs in this list
and perhaps further language related bugs would be easier to detect if
they were in the same file.
I don't think so.
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
+(defconst org-export-dictionary
Why?
Because it is not meant to be changed by the user nor let-bound. IOW,
it's a
Nicolas Goaziou n.goaz...@gmail.com writes:
Even though it is a defconst, you can still change it. You are not
forced to anything. But you're on your own.
By the way, it is a defconst because of the keys, which shouldn't be
altered, not the values.
It /may/ be converted to a defcustom.
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Even though it is a defconst, you can still change it. You are not
forced to anything. But you're on your own.
By the way, it is a defconst because of the keys, which shouldn't be
altered, not the
Nicolas Goaziou n.goaz...@gmail.com writes:
Of course. Patch welcome.
The conversation is taking a humorous turn.
Nicolas Goaziou n.goaz...@gmail.com writes:
Even though it is a defconst, you can still change it. You are not
forced to anything. But you're on your own.
I agree, but it being a defconst, it comes with the message
This declares that neither programs nor users should ever change
the
Rasmus ras...@gmx.us writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Even though it is a defconst, you can still change it. You are not
forced to anything. But you're on your own.
I agree, but it being a defconst, it comes with the message
This declares that neither programs nor
Hello,
Rasmus wrote:
Nicolas Goaziou n.goaz...@gmail.com writes:
I would like to move every variable and function related to
internationalization (i.e smart quotes and translations) in a dedicated
file (ox-i18n.el) instead of ox.el.
Sounds good to me.
+1
How about a more informative
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
Sounds good to me.
+1
Let's clearly think about what problem it is supposed to solve:
if it is just discoverability for potential contributors, I don't
think it's worth the split.
--
Bastien
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
I would like to move every variable and function related to
internationalization (i.e smart quotes and translations) in a dedicated
file (ox-i18n.el) instead of ox.el.
Considering ox.el is 6k lines long, I think it can be a bit tedious
Nicolas Goaziou n.goaz...@gmail.com writes:
I would like to move every variable and function related to
internationalization (i.e smart quotes and translations) in a dedicated
file (ox-i18n.el) instead of ox.el.
Sounds good to me.
How about a more informative name where uninformed need not
15 matches
Mail list logo
