Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Inconsistencies in JSON to POT conversion process #32

Open
edmoss345 opened this issue Mar 16, 2023 · 1 comment
Open

Inconsistencies in JSON to POT conversion process #32

edmoss345 opened this issue Mar 16, 2023 · 1 comment

Comments

@edmoss345
Copy link
Collaborator 

          This is working well, I've tested both scripts.

I came across one point of improvement that I hadn't mentioned to you before:
For some reason certain strings in the .json get split into multiple substrings (some of which are empty) in the .pot file. These later get merged into fewer strings by Crowdin, and so this twice causes a whole lot of changes that are not easy to check. I'm not exactly sure what's the "rule" that Crowdin is following for its splitting into substrings - but for sure every string of the form msgid "" "Some text" gets replaced by msgid "Some text. If you have some future improvement to suggest here that would be great.

image

image

Originally posted by @esmeetewinkel in #31 (review)
@edmoss345
Copy link
Collaborator Author

@esmeetewinkel I've got a bit of capacity this week, is the above still an issue that I can take a look at?

@istride istride moved this to Todo in ParentText Sep 6, 2023
@fagiothree fagiothree moved this from Todo to Backlog in ParentText Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
ParentText
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@edmoss345