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

i18n: Staff/public interface footer is not ready for i18n #2583

Closed
nebulon42 opened this issue Dec 25, 2021 · 0 comments · Fixed by #2586
Closed

i18n: Staff/public interface footer is not ready for i18n #2583

nebulon42 opened this issue Dec 25, 2021 · 0 comments · Fixed by #2586

Comments

@nebulon42
Copy link
Contributor

Expected Behavior

Footers (_footer.html.erb) of public and staff interface contain text which is ready for i18n and can be localized.

Current Behavior

Footers (_footer.html.erb) of public and staff interface are not ready for i18n and are always displayed in English no matter which language is selected.

Your Environment

  • Version used: 3.1.1
  • Environment name and version (e.g. Chrome 39, node.js 5.4): N/A
  • Operating System and version (desktop or mobile): N/A
  • Link to your project: N/A
nebulon42 added a commit to nebulon42/archivesspace that referenced this issue Dec 27, 2021
@nebulon42
add i18n to frontend and public interface footers, fixes archivesspac…
1eef947 
…e#2583
@nebulon42 nebulon42 mentioned this issue Dec 27, 2021
Merged
9 tasks
nebulon42 added a commit to nebulon42/archivesspace that referenced this issue Dec 27, 2021
@nebulon42
add i18n to frontend and public interface footers, fixes archivesspac…
117a2a1 
…e#2583
@nebulon42 nebulon42 changed the title Staff/public interface footer is not ready for i18n i18n: Staff/public interface footer is not ready for i18n Jan 18, 2022
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
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add i18n to frontend and public interface footers nebulon42/archivesspace
1 participant
@nebulon42