Differences between revisions 8 and 9
Revision 8 as of 2015-12-23 04:57:12
Size: 2090
Comment: Update default password and ./setup.py related instructions (also same as previous changes)
Revision 9 as of 2016-03-26 12:05:14
Size: 2733
Comment: fix image link, headline=page name, notes in separate section, add reboot note, minor language fixes
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Test User Interface Translations = = Testing Plinth Translation =
Line 5: Line 5:
If you want to test Plinth (!FreedomBox user interface) translations you can use a Virtualbox image, please follow these steps.  If you want to test an unreleased Plinth (!FreedomBox user interface) translation you can use a previous Virtualbox image on a host computer, and update it with the latest Plinth and your translation.
Line 7: Line 7:
 * Setup a !VirtualBox !FreedomBox as described on [[FreedomBox/Hardware/VirtualBox|VirtualBox image page]] (this recipe based on the [[http://ftp.skolelinux.org/pub/freedombox/latest/freedombox-unstable-free_2015-10-18_virtualbox-amd64.tar.bz2|2015-10-18 image]]) Please follow these steps.
Line 9: Line 9:
 * Boot !FreedomBox and go to Plinth in browser on host (https://fbx-ip). Complete the first boot setup process. During the process, you will create and administrator account. Use this account to login in the next step.  * Setup a !VirtualBox !FreedomBox as described on [[FreedomBox/Hardware/VirtualBox|VirtualBox image page]] (this recipe based on the [[http://ftp.skolelinux.org/pub/freedombox/0.6/freedombox-unstable-free_2015-10-18_virtualbox-amd64.tar.bz2|2015-10-18 image]]).
Line 11: Line 11:
 * Access the terminal and login with the administrator account during first boot process.  * Boot !FreedomBox and access Plinth in a browser on host (https://fbx-ip). Complete the first boot setup process. During the process, you will create a system user account on Debian (administrator account). Use this account to login in the next step.

 * Access the terminal (eg. in the !VirtualBox window or through ssh) and login with the administrator account created during above first boot process.
Line 21: Line 23:
 * Download django.po from Weblate or use your local copy and place it in ~/Plinth/plinth/locale/<yourlanguage>/LC_MESSAGES/ (download on host, transfer to guest using e.g. scp or !VirtualBox Shared Folders)  * Fetch the translation you want to test, by eg. downloading django.po from Weblate/GitHub or use your local copy and place it in ~/Plinth/plinth/locale/<yourlanguage>/LC_MESSAGES/ (download on host, transfer to guest using e.g. scp or !VirtualBox Shared Folders)
Line 29: Line 31:
 * Go to Plinth in browser on host (https://fbx-ip). For Plinth to automatically show interface in your language, make sure that your browser language settings has your language as first choice. Alternatively, change your locale in System Configuration (gears symbol upper right)->Configure->Language (https://fbx-ip/plinth/sys/config/)  * Go to Plinth in browser on host (https://fbx-ip). For Plinth to automatically show its interface in your language, make sure that your browser language settings has your language as first choice. Alternatively, change your locale in System Configuration (gears symbol upper right)->Configure->Language (https://fbx-ip/plinth/sys/config/)
Line 33: Line 35:
 * To update .po with new strings from source code run (.po needs review after this!): == Notes ==

The procedure outlined here might break and become non-functional at any time because it follows development master branch in git which changes constantly.

 * After reboot of the !VirtualBox system the old Plinth will be restarted automatically. Do like this to stop it and start the new.
Line 35: Line 41:
sudo service plinth stop
cd ~/Plinth
sudo ./run --debug --no-daemon
}}}

 * To run the latest Plinth update source code from !GitHub :
  {{{
cd ~/Plinth
git pull
}}}

 * To update .po files with new strings from source code run (.po needs review after this!):
  {{{
cd ~/Plinth
Line 38: Line 58:
NOTE: Any of this may break at any time because it follows development master branch in git which changes constantly.

Testing Plinth Translation

If you want to test an unreleased Plinth (FreedomBox user interface) translation you can use a previous Virtualbox image on a host computer, and update it with the latest Plinth and your translation.

Please follow these steps.

  • Setup a VirtualBox FreedomBox as described on VirtualBox image page (this recipe based on the 2015-10-18 image).

  • Boot FreedomBox and access Plinth in a browser on host (https://fbx-ip). Complete the first boot setup process. During the process, you will create a system user account on Debian (administrator account). Use this account to login in the next step.

  • Access the terminal (eg. in the VirtualBox window or through ssh) and login with the administrator account created during above first boot process.

    • sudo apt-get update
      sudo apt-get install gettext
      sudo mv /etc/plinth/plinth.config /etc/plinth/plinth.config_disabled 
      git clone https://github.com/freedombox/Plinth
      cd ~/Plinth
      nano plinth.config (change line 8 to read "server_dir = /plinth")
  • Fetch the translation you want to test, by eg. downloading django.po from Weblate/GitHub or use your local copy and place it in ~/Plinth/plinth/locale/<yourlanguage>/LC_MESSAGES/ (download on host, transfer to guest using e.g. scp or VirtualBox Shared Folders)

  • To prepare translation and run new plinth do:
    • sudo service plinth stop
      ./setup.py compile_translations
      sudo ./run --debug --no-daemon
  • Go to Plinth in browser on host (https://fbx-ip). For Plinth to automatically show its interface in your language, make sure that your browser language settings has your language as first choice. Alternatively, change your locale in System Configuration (gears symbol upper right)->Configure->Language (https://fbx-ip/plinth/sys/config/)

  • Enjoy your translation!

Notes

The procedure outlined here might break and become non-functional at any time because it follows development master branch in git which changes constantly.

  • After reboot of the VirtualBox system the old Plinth will be restarted automatically. Do like this to stop it and start the new.

    • sudo service plinth stop
      cd ~/Plinth
      sudo ./run --debug --no-daemon
  • To run the latest Plinth update source code from GitHub :

    • cd ~/Plinth
      git pull
  • To update .po files with new strings from source code run (.po needs review after this!):
    • cd ~/Plinth
      ./setup.py update_translations


Intro

Information

Support

Contribute

Reports

Promote

Vision

Hardware

Live Help

Where To Start

Translate

Calls

Talks

Overview

Download

Q&A

To Do

Design

Releases

Press

Features

Manual

Contributors

Code

Blog

FreedomBox for Communities

FreedomBox Developer Manual

HELP & DISCUSSIONS: Discussion Forum - Mailing List - #freedombox irc.debian.org | CONTACT Foundation | JOIN Project

Next call: Sunday, October 24 at 17:00 UTC

This page is copyright its contributors and is licensed under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.


CategoryFreedomBox