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.

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

Update #162

Merged
merged 143 commits into from
May 15, 2024
Merged

Update #162

merged 143 commits into from
May 15, 2024

Conversation

linearcombination
Copy link
Contributor

Please see commits for what is in this pull request.

Sorry for the big PR. I was doing so great giving you smaller PRs, I will get back to that.

Handle RTL languages even when mixed with LTR languages which is not
possible using only html dir directive, it is much more complicated
than that and we also implemented same for Docx which is handled
completely differently under the hood.
Displaay english language name in parens next to localized name. Note
that some languages have their localized name as, say,
Francais (French), when they should have only proided Francais as the
localized name. Because they did this you get
Francais (French) (French) as the outcome.
* Implements #152
* Implements #154
* Implements #146
* Implements #156
* Fix #160
* Implements #158
* Fix #157
* Fix #159
@linearcombination linearcombination temporarily deployed to doc-dev.walink.org August 29, 2023 00:41 — with GitHub Actions Inactive
In translation.json a language has a localized name and its English
name. Unfortunately, many languages have included the English
name (usually in parens) in the slot designated for localized name
only. Further we display the English name next to the localized name
in the UI by requirement and so for those languages with this data
problem they end up having a name presentation like 'Foo (Bar) (Bar)'.
So this commit adds some logic to detect if the English name has been
erroneously included in the localized name and if it has it does not
add the English name in parens (since it is already there), otherwise
it does add the English name.
@linearcombination linearcombination temporarily deployed to doc-dev.walink.org September 1, 2023 23:42 — with GitHub Actions Inactive
@linearcombination linearcombination temporarily deployed to doc-dev.walink.org September 2, 2023 22:24 — with GitHub Actions Inactive
@linearcombination linearcombination temporarily deployed to doc-dev.walink.org September 3, 2023 00:03 — with GitHub Actions Inactive
To match figma design for mobile
Make active state match figma by UX team request
They can still navigate away from page and lose state by clicking
links that go elsewhere. A future update may prevent or warn on that
as well.
This update allows the user to navigate within-app away from the
document generation page and return without losing the document
generation task status state. Further, if the user tries to reload or
close the tab while a document is being generated, the user is
presented with a system dialog asking if them to confirm their intent
or cancel the reload/close action.
By request of UX team
Also adjust the search input field for languages and books to have a
little left margin
* Handle transfer URLs from BIEL with fully populated UI state
* New (required) env var name changes for sveltekit env var system
* Nginx config is now separate from node config and envvars js hack is
no longer needed because sveltekit handles this with the new env var system
@PurpleGuitar PurpleGuitar temporarily deployed to doc-dev.walink.org May 13, 2024 15:54 — with GitHub Actions Inactive
@PurpleGuitar PurpleGuitar merged commit 77818a1 into doc.bibleineverylanguage.org May 15, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants