[
https://issues.apache.org/jira/browse/JSPWIKI-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134732#comment-18134732
]
Arturo Bernal commented on JSPWIKI-1182:
----------------------------------------
Numbers from master for the order of the literals, counting adjacent keys in
the file that are out of alphabetical order, ignoring case: default.properties
of the templates has 512 keys and 217 adjacent pairs out of order, and
CoreResources.properties has 126 keys and 67 pairs out of order. So the files
are not in alphabetical order today. These two are the English files only; the
translated files and the use of each key in the JSPs were not looked at.
Leaving the issue open.
> Reorder and Rename i18n Literals According to Usage Context
> -----------------------------------------------------------
>
> Key: JSPWIKI-1182
> URL: https://issues.apache.org/jira/browse/JSPWIKI-1182
> Project: JSPWiki
> Issue Type: Improvement
> Affects Versions: 2.12.1
> Reporter: Arturo Bernal
> Priority: Minor
>
> In the recent pull request addressing missing i18n literals (JSPWIKI-925), it
> was noted that the literals are not in alphabetical order. Additionally, the
> current ordering loosely follows the order of JSPs, which may not be the most
> intuitive way to manage them.
> This ticket aims to address the following:
> # Reorder the i18n literals alphabetically or according to a more logical or
> intuitive scheme.
> # Consider renaming the literals to better reflect where they are being used
> in the application.
> By tackling these issues in a separate ticket, we can maintain a cleaner,
> more organized codebase and make it easier for contributors to locate and
> manage i18n literals in the future.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
