Skip to content

Enhancement: a clear guide for ldf vs. ini selection needed (documentation revamping). #311

Open
@niruvt

Description

@niruvt

Have a look at 1, 2.

I asked these questions in order to adhere to the best practices for as many languages as I can. Of course, nobody can have everything by heart since the information stored in this package is humongous, but what I struggled with is that there was no precise information available about which language is best supported with which way, i.e., ldf or ini (and why so). Generally it is assumed that the user will read the documentation, online resources, guidelines and then select the best method available, but seldom the ground-level users take this much effort. I was trying to develop something that will take care of "most of the things" related to language, but realised there is way to much to this area than I thought. Most of the peers advised me to leave babel up to users and develop the rest of the code, but this idea didn't impress me much.

Forget about development, suppose somebody wants to do cool things in their local files using a lot of languages, even then whether the ldf or the ini wasn't very clearly described in the resources I found.

Sorry for the longish introduction, but I feel it was needed to establish the requirement I am suggesting. We need a development tracker (maybe a table) which clearly marks the progress of the ldf-s and ini. I would love to work for this. The idea I have is not much different than 3, but I require an one-stop location for all the information regarding language LaTeX. Let me know what you think, how I can help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions