Merge lp:~emailgirishrawat/ubuntu-filemanager-app/READMEs into lp:ubuntu-filemanager-app

Proposed by Girish on 2015-12-19
Status: Merged
Approved by: Arto Jalkanen on 2015-12-23
Approved revision: 511
Merged at revision: 511
Proposed branch: lp:~emailgirishrawat/ubuntu-filemanager-app/READMEs
Merge into: lp:ubuntu-filemanager-app
Diff against target: 653 lines (+331/-270)
10 files modified
README (+0/-169)
README-Autopilot.md (+19/-0)
README-ContentHubDesktop.md (+63/-0)
README-Developers.md (+151/-0)
README-Mergeproposal (+28/-0)
README-Translations.md (+38/-0)
README.contentHubDesktop (+0/-65)
README.md (+26/-0)
README.translations (+0/-36)
debian/changelog (+6/-0)
To merge this branch: bzr merge lp:~emailgirishrawat/ubuntu-filemanager-app/READMEs
Reviewer Review Type Date Requested Status
Jenkins Bot continuous-integration Approve on 2015-12-23
Arto Jalkanen 2015-12-19 Approve on 2015-12-19
Review via email: mp+281007@code.launchpad.net

Commit message

Updated and expanded READMEs.

Description of the change

Improved READMEs.

To post a comment you must log in.
Arto Jalkanen (ajalkane) wrote :

Thank you!

review: Approve

FAILED: Autolanding.
No commit message was specified in the merge proposal. Hit 'Add commit message' on the merge proposal web page or follow the link below. You can approve the merge proposal yourself to rerun.
https://code.launchpad.net/~emailgirishrawat/ubuntu-filemanager-app/READMEs/+merge/281007/+edit-commit-message

review: Needs Fixing (continuous-integration)
Girish (emailgirishrawat) wrote :

Arto: Have added a commit message. CAn you approve this again?

review: Approve (continuous-integration)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== removed file 'README'
2--- README 2014-11-11 19:20:57 +0000
3+++ README 1970-01-01 00:00:00 +0000
4@@ -1,169 +0,0 @@
5-# Ubuntu File Manager
6-
7-File manager app for Ubuntu on the desktop and on mobile devices.
8-
9-## Building the app
10-
11-### For the desktop
12-
13-Install the following build dependencies:
14-
15- sudo apt-get install libtag1-dev libpam0g-dev python3
16-
17-Then open the CMakeLists.txt file in Qt Creator, and ensure that the kit
18-selected on the left sidebar (just above the green "Run" button) is "Desktop"
19-
20-### For a device
21-
22-If you don't have one already, you'll need to create an armhf chroot to
23-cross-compile the app (also do this if you have an older armhf chroot, for
24-example 14.04 and current target is 14.10. You can first delete the old target
25-and then create a current one). Here's how:
26-
27-1. In Qt Creator, open the CMakeLists.txt file
28-2. Go to Tools > Options > Ubuntu > Click
29-2. Click on Create Click Target
30-3. Follow the prompts to generate the chroot. You will be asked for your sudo
31- password
32-4. Once created, you'll need to add the build dependencies for the app:
33- - Click on the Maintain button on your chroot
34- - On the terminal prompt that is started, type
35- apt-get install libtag1-dev:armhf libpam0g-dev:armhf python3
36- - Close the terminal when the installation finishes
37-5. Now you can either do a clean checkout and wait to be prompted by Qt Creator
38- to add the armhf kit, or alternatively:
39-6. Go to the Projects tab > Add kit and then select the UbuntuSDK armhf kit
40-
41-Additionally, you'll have to tell Qt Creator that you are doing a build for a
42-device to ultimately create a click package for installation:
43-
44-1. In Qt Creator, go to the Projects tab on the sidebar
45-2. Click on the "Build" subtab of the "UbuntuSDK for armhf..." tab
46-3. Then go to the "CMake arguments" text field and add "-DCLICK_MODE=on"
47- without the quotes
48-
49-Before starting the build make sure to select the "UbuntuSDK" kit on Qt
50-Creator's left sidebar (just above the green "Run" button).
51-
52-### Doing the build
53-
54-Ensure you've selected the kit you want for your build and press the build
55-button on Qt Creator's left sidebar (or alternatively Ctrl+B).
56-
57-## Running the app
58-
59-### On the desktop
60-
61-No additional steps are required before running the app on the desktop.
62-
63-You can pass two switches to run in phone or tablet mode from the desktop:
64-
65--p for phone mode
66--t for tablet mode
67-
68-
69-### On a device
70-
71-Due to Qt Creator's bug #1312094 in launchpad.net, there needs to be a manual
72-workaround done before the app can run on the device:
73-
74-1. Modify the desktop.in file: change the Exec line to read:
75- Exec=lib/arm-linux-gnueabihf/bin/@EXEC@
76-
77-Remember to revert this temporary change if you are building a click package or
78-if you're making other changes to be committed to the code!
79-
80-### Starting the app
81-
82-Ensure you've selected the kit you want for your build and press the run
83-button on Qt Creator's left sidebar (or alternatively Ctrl+R).
84-
85-If the app hasn't been built yet, or if there are pending changes that require
86-a build, the app will automatically be built first before running.
87-
88-If you're starting the app on a device, the build will be copied over and the
89-code will run unconfined.
90-
91-## Building a click package
92-
93-There are two alternative ways of building a click package.
94-
95-### Using Qt Creator
96-
97-1. Ensure you've selected the UbuntuSDK for armhf kit on Qt Creator's sidebar
98-2. Click on Publish on the sidebar
99-3. Click on "Create package"
100-4. If all goes well, you'll find the final click package in the build directory
101-
102-Notes:
103-- You can see the output of the click build if you click on Edit on the sidebar
104- and then "Application Output" at the bottom. This is useful to identify any
105- failures during the build
106-- Run `sudo apt-get install click-reviewers-tools` to enable click package
107- validation in Qt Creator. You might need to restart Qt Creator after you've
108- installed them for it to detect them
109-
110-### Using click-buddy
111-
112-1. Install phablet-tools: `sudo apt-get install phablet-tools`
113-2. Run click-buddy in your source tree:
114- click-buddy --dir . --arch armhf --framework ubuntu-sdk-14.04
115-3. Once finished, click-buddy will tell you the location of your source package
116-
117-## Installing a click package
118-
119-First of all, ensure you've got a working Ubuntu device attached over USB to
120-your host computer
121-
122-### Manually
123-
124-Run the following commands to manually install the click package (replace 0.5
125-with the version of your package):
126-
127- adb push com.ubuntu.filemanager_0.3.latest_armhf.click /home/phablet/
128- adb shell
129- sudo -H -u phablet pkcon install-local /home/phablet/com.ubuntu.filemanager_0.3_armhf.click
130-
131-### Using click-buddy
132-
133-You can add the --provision argument to the previous command to install the
134-click package on the device.
135-
136-### Starting the app
137-
138-1. Either kill unity8 with `pkill unity8` or restart the system for the Apps
139- (click) scope to pick up your newly installed click package
140-2. Search for Reminders in the Apps scope and tap on its icon to start it
141-3. You'll find the runtime logs at ~/.cache/upstart/application-click/
142-
143-## Uninstalling a click package
144-
145-Run the following commands, replacing the version of the click package you want
146-to uninstall:
147-
148- adb shell
149- sudo -iu phablet
150- sudo click unregister com.ubuntu.filemanager 0.3
151-
152-## Run the autopilot tests
153-
154-Prerequisites:
155- sudo apt-get install ubuntu-ui-toolkit-autopilot
156-
157-Once the app has been built, you can go to the build directory and run:
158-
159- cd tests/autopilot
160- autopilot3 run filemanager
161-
162-You can run filemanager in phone or tablet mode passing one of these two switches:
163-
164--p for phone mode
165--t for tablet mode
166-
167-so:
168-
169-autopilot3 launch ../../src/app/filemanager -p
170-
171-will launch filemanager with autopilot in phone mode.
172-
173-
174
175=== added file 'README-Autopilot.md'
176--- README-Autopilot.md 1970-01-01 00:00:00 +0000
177+++ README-Autopilot.md 2015-12-19 07:36:54 +0000
178@@ -0,0 +1,19 @@
179+ReadMe - Run Autopilot tests
180+============================
181+
182+# Prerequisites
183+* ubuntu-ui-toolkit-autopilot : sudo apt-get install ubuntu-ui-toolkit-autopilot
184+
185+# Next Steps
186+Once the app has been built, you can go to the build directory and run:
187+
188+ cd tests/autopilot
189+ autopilot3 run filemanager
190+
191+You can run filemanager in phone or tablet mode passing one of these two switches:
192+
193+-p for phone mode
194+-t for tablet mode
195+
196+* autopilot3 launch ../../src/app/filemanager -p will launch filemanager with autopilot in phone mode
197+* autopilot3 launch ../../src/app/filemanager -t will launch filemanager with autopilot in tablet mode.
198
199=== added file 'README-ContentHubDesktop.md'
200--- README-ContentHubDesktop.md 1970-01-01 00:00:00 +0000
201+++ README-ContentHubDesktop.md 2015-12-19 07:36:54 +0000
202@@ -0,0 +1,63 @@
203+Testing Content-Hub support
204+===========================
205+
206+## For the desktop
207+
208+Install the following dependencies to run click applications:
209+
210+ sudo apt-get install upstart-app-launch-tools
211+
212+### Build FileManager and install FileManager as click package
213+
214+Build FileManager as a click package and install it. At the time of this writing
215+this doesn't seem to be working with the SDK (due to cmake), but it can be done
216+from command line:
217+
218+First you must modify manifest.json and replace "architecture" value of "armhf" with "i386".
219+Just remember to change it back to armhf if you commit changes.
220+
221+After that you can build x86 version of the package and install it:
222+
223+ QT_SELECT=qt5 cmake . -DCLICK_MODE=1 && make -j2 && make install DESTDIR=install && click build install
224+ sudo click install --user=$USER ./com.ubuntu.filemanager_0.3.latest_i386.click
225+
226+### Build and install hub-importer as click package
227+
228+Get the sources for building:
229+
230+ bzr branch lp:~ken-vandine/+junk/hub-importer
231+
232+You should be able to create click package out of it in SDK by opening the project and using Publish and Create package.
233+
234+Install the created package (example):
235+
236+ sudo click install --user=$USER com.ubuntu.developer.ken-vandine.hub-importer_0.2_all.click
237+
238+### Running test
239+
240+Run hub-importer (example):
241+
242+ upstart-app-launch com.ubuntu.developer.ken-vandine.hub-importer_hub-importer_0.2
243+
244+Click "Select source" button.
245+
246+You should see File Manager as one of the choices. If you do not see File Manager, look at "Troubleshooting" section.
247+Click on File Manager, and File Manager should start. Now you should choose some pictures as that's the only thing
248+supported at the moment (even though FileManager allows selecting any type). You can select multiple files in a
249+directory if you so choose. Once you're satisfied with the seelction, click "Select". You should see the pictures
250+then in Hub Importer.
251+
252+Troubleshooting
253+===============
254+
255+* If you don't see File Manager as one of the choises in Hub Importer, then quit Hub Importer and run this script:
256+ /usr/lib/i386-linux-gnu/content-hub/content-hub-peer-hook
257+ Try running Hub Importer again after that and File Manager should show.
258+ If the above script does not exist, you can try locating something similar with:
259+ locate hook
260+* If you have trouble running Hub Importer or the above still doesn't work, check the installed click packages with:
261+ click list
262+ It should show entry for both File Manager and Hub Importer. If it does not, installing the click package has not succeeded
263+* If all else fails, check the logs for both Hub Importer and File Manager for further clues at:
264+ $HOME/.cache/upstart/
265+
266
267=== added file 'README-Developers.md'
268--- README-Developers.md 1970-01-01 00:00:00 +0000
269+++ README-Developers.md 2015-12-19 07:36:54 +0000
270@@ -0,0 +1,151 @@
271+Building the app
272+================
273+
274+### For the desktop
275+
276+Install the following build dependencies:
277+
278+ sudo apt-get install libtag1-dev libpam0g-dev python3
279+
280+Then open the CMakeLists.txt file in Qt Creator, and ensure that the kit
281+selected on the left sidebar (just above the green "Run" button) is "Desktop"
282+
283+### For a device
284+
285+If you don't have one already, you'll need to create an armhf chroot to
286+cross-compile the app (also do this if you have an older armhf chroot, for
287+example 14.04 and current target is 14.10. You can first delete the old target
288+and then create a current one). Here's how:
289+
290+1. In Qt Creator, open the CMakeLists.txt file
291+2. Go to Tools > Options > Ubuntu > Click
292+2. Click on Create Click Target
293+3. Follow the prompts to generate the chroot. You will be asked for your sudo
294+ password
295+4. Once created, you'll need to add the build dependencies for the app:
296+ - Click on the Maintain button on your chroot
297+ - On the terminal prompt that is started, type
298+ apt-get install libtag1-dev:armhf libpam0g-dev:armhf python3
299+ - Close the terminal when the installation finishes
300+5. Now you can either do a clean checkout and wait to be prompted by Qt Creator
301+ to add the armhf kit, or alternatively:
302+6. Go to the Projects tab > Add kit and then select the UbuntuSDK armhf kit
303+
304+Additionally, you'll have to tell Qt Creator that you are doing a build for a
305+device to ultimately create a click package for installation:
306+
307+1. In Qt Creator, go to the Projects tab on the sidebar
308+2. Click on the "Build" subtab of the "UbuntuSDK for armhf..." tab
309+3. Then go to the "CMake arguments" text field and add "-DCLICK_MODE=on"
310+ without the quotes
311+
312+Before starting the build make sure to select the "UbuntuSDK" kit on Qt
313+Creator's left sidebar (just above the green "Run" button).
314+
315+### Doing the build
316+
317+Ensure you've selected the kit you want for your build and press the build
318+button on Qt Creator's left sidebar (or alternatively Ctrl+B).
319+
320+
321+Running the app
322+===============
323+
324+### On the desktop
325+
326+No additional steps are required before running the app on the desktop.
327+
328+You can pass two switches to run in phone or tablet mode from the desktop:
329+
330+-p for phone mode
331+-t for tablet mode
332+
333+
334+### On a device
335+
336+Due to Qt Creator's bug #1312094 in launchpad.net, there needs to be a manual
337+workaround done before the app can run on the device:
338+
339+1. Modify the desktop.in file: change the Exec line to read:
340+ Exec=lib/arm-linux-gnueabihf/bin/@EXEC@
341+
342+Remember to revert this temporary change if you are building a click package or
343+if you're making other changes to be committed to the code!
344+
345+### Starting the app
346+
347+Ensure you've selected the kit you want for your build and press the run
348+button on Qt Creator's left sidebar (or alternatively Ctrl+R).
349+
350+If the app hasn't been built yet, or if there are pending changes that require
351+a build, the app will automatically be built first before running.
352+
353+If you're starting the app on a device, the build will be copied over and the
354+code will run unconfined.
355+
356+
357+Building a click package
358+========================
359+
360+There are two alternative ways of building a click package.
361+
362+### Using Qt Creator
363+
364+1. Ensure you've selected the UbuntuSDK for armhf kit on Qt Creator's sidebar
365+2. Click on Publish on the sidebar
366+3. Click on "Create package"
367+4. If all goes well, you'll find the final click package in the build directory
368+
369+Notes:
370+- You can see the output of the click build if you click on Edit on the sidebar
371+ and then "Application Output" at the bottom. This is useful to identify any
372+ failures during the build
373+- Run `sudo apt-get install click-reviewers-tools` to enable click package
374+ validation in Qt Creator. You might need to restart Qt Creator after you've
375+ installed them for it to detect them
376+
377+### Using click-buddy
378+
379+1. Install phablet-tools: `sudo apt-get install phablet-tools`
380+2. Run click-buddy in your source tree:
381+ click-buddy --dir . --arch armhf --framework ubuntu-sdk-14.04
382+3. Once finished, click-buddy will tell you the location of your source package
383+
384+
385+Installing a click package
386+==========================
387+
388+First of all, ensure you've got a working Ubuntu device attached over USB to
389+your host computer
390+
391+### Manually
392+
393+Run the following commands to manually install the click package (replace 0.5
394+with the version of your package):
395+
396+ adb push com.ubuntu.filemanager_0.3.latest_armhf.click /home/phablet/
397+ adb shell
398+ sudo -H -u phablet pkcon install-local /home/phablet/com.ubuntu.filemanager_0.3_armhf.click
399+
400+### Using click-buddy
401+
402+You can add the --provision argument to the previous command to install the
403+click package on the device.
404+
405+### Starting the app
406+
407+1. Either kill unity8 with `pkill unity8` or restart the system for the Apps
408+ (click) scope to pick up your newly installed click package
409+2. Search for Reminders in the Apps scope and tap on its icon to start it
410+3. You'll find the runtime logs at ~/.cache/upstart/application-click/
411+
412+
413+Uninstalling a click package
414+============================
415+
416+Run the following commands, replacing the version of the click package you want
417+to uninstall:
418+
419+ adb shell
420+ sudo -iu phablet
421+ sudo click unregister com.ubuntu.filemanager 0.3
422
423=== added file 'README-Mergeproposal'
424--- README-Mergeproposal 1970-01-01 00:00:00 +0000
425+++ README-Mergeproposal 2015-12-19 07:36:54 +0000
426@@ -0,0 +1,28 @@
427+Prerequisites to approving a Merge Proposal (MP)
428+================================================
429+
430+Over time, it has been found that insufficient testing by reviewers sometimes leads to file manager app trunk not buildable in Qtcreator due to manifest errors, or translation pot file not updated. As such, please follow the checklist below before top-approving a MP.
431+
432+Checklist
433+=========
434+
435+* Does the MP add/remove user visible strings? If Yes, has the pot file been
436+ updated?
437+
438+* Does the MP change the UI? If Yes, has it been approved by design?
439+
440+* Did you perform an exploratory manual test run of your code change and any
441+ related functionality?
442+
443+* If the MP fixes a bug or implements a feature, are there accompanying unit
444+ and autopilot tests?
445+
446+* Is the file manager app trunk buildable and runnable using Qtcreator?
447+
448+* Was the debian changelog updated?
449+
450+* Was the copyright years updated if necessary?
451+
452+The above checklist is more of a guideline to help file manager app trunk stay buildable,
453+stable and up to date.
454+
455
456=== added file 'README-Translations.md'
457--- README-Translations.md 1970-01-01 00:00:00 +0000
458+++ README-Translations.md 2015-12-19 07:36:54 +0000
459@@ -0,0 +1,38 @@
460+Updating translations
461+=====================
462+
463+Translations for the Filemanager app happen in [Launchpad Translations](https://translations.launchpad.net/ubuntu-filemanager-app) and
464+are automatically committed daily on the trunk branch in the po/ folder.
465+
466+They are then built and installed as part of the package build, so that
467+developers don't really need to worry about them.
468+
469+However, there is one task that needs to be taken care of: exposing new
470+translatable messages to translators. So whenever you add new translatable
471+messages in the code, make sure to follow these steps:
472+
473+ 1. Run click-buddy retaining the build directory:
474+ `click-buddy --dir . --no-clean`
475+ 2. Commit the generated .pot file: `bzr commit -m"Updated translation template"`
476+ 3. Push the branch and send a merge proposal as usual
477+
478+And that's it, once the branch lands Launchpad should take care of all the rest!
479+
480+Behind the scenes
481+=================
482+
483+Behind the scenes, whenever the po/*.pot file (also known as translations template)
484+is committed to trunk Launchpad reads it and updates the translatable strings
485+exposed in the web UI. This will enable translators to work on the new strings.
486+The translations template contains all translatable strings that have been
487+extracted from the source code files.
488+
489+Launchpad will then store translations in its database and will commit them daily
490+in the form of textual po/*.po files to trunk. The PO files are also usually
491+referred to as the translations files. You'll find a translation file for each
492+language the app has got at least a translated message available for.
493+
494+Translations for core apps follow the standard [gettext format](https://www.gnu.org/software/gettext/).
495+
496+ [Launchpad Translations](https://translations.launchpad.net/ubuntu-filemanager-app)
497+ [gettext format](https://www.gnu.org/software/gettext/)
498
499=== removed file 'README.contentHubDesktop'
500--- README.contentHubDesktop 2014-07-01 21:55:07 +0000
501+++ README.contentHubDesktop 1970-01-01 00:00:00 +0000
502@@ -1,65 +0,0 @@
503-# Ubuntu File Manager
504-
505-File manager app for Ubuntu on the desktop and on mobile devices.
506-
507-## Testing Content-Hub support
508-
509-### For the desktop
510-
511-Install the following dependencies to run click applications:
512-
513- sudo apt-get install upstart-app-launch-tools
514-
515-#### Build FileManager and install FileManager as click package
516-
517-Build FileManager as a click package and install it. At the time of this writing
518-this doesn't seem to be working with the SDK (due to cmake), but it can be done
519-from command line:
520-
521-First you must modify manifest.json and replace "architecture" value of "armhf" with "i386".
522-Just remember to change it back to armhf if you commit changes.
523-
524-After that you can build x86 version of the package and install it:
525-
526- QT_SELECT=qt5 cmake . -DCLICK_MODE=1 && make -j2 && make install DESTDIR=install && click build install
527- sudo click install --user=$USER ./com.ubuntu.filemanager_0.3.latest_i386.click
528-
529-#### Build and install hub-importer as click package
530-
531-Get the sources for building:
532-
533- bzr branch lp:~ken-vandine/+junk/hub-importer
534-
535-You should be able to create click package out of it in SDK by opening the project and using Publish and Create package.
536-
537-Install the created package (example):
538-
539- sudo click install --user=$USER com.ubuntu.developer.ken-vandine.hub-importer_0.2_all.click
540-
541-#### Running test
542-
543-Run hub-importer (example):
544-
545- upstart-app-launch com.ubuntu.developer.ken-vandine.hub-importer_hub-importer_0.2
546-
547-Click "Select source" button.
548-
549-You should see File Manager as one of the choices. If you do not see File Manager, look at "Troubleshooting" section.
550-Click on File Manager, and File Manager should start. Now you should choose some pictures as that's the only thing
551-supported at the moment (even though FileManager allows selecting any type). You can select multiple files in a
552-directory if you so choose. Once you're satisfied with the seelction, click "Select". You should see the pictures
553-then in Hub Importer.
554-
555-#### Troubleshooting
556-
557- - If you don't see File Manager as one of the choises in Hub Importer, then quit Hub Importer and run this script:
558- /usr/lib/i386-linux-gnu/content-hub/content-hub-peer-hook
559- Try running Hub Importer again after that and File Manager should show.
560- If the above script does not exist, you can try locating something similar with:
561- locate hook
562- - If you have trouble running Hub Importer or the above still doesn't work, check the installed click packages with:
563- click list
564- It should show entry for both File Manager and Hub Importer. If it does not, installing the click package has not succeeded
565- - If all else fails, check the logs for both Hub Importer and File Manager for further clues at:
566- $HOME/.cache/upstart/
567-
568
569=== added file 'README.md'
570--- README.md 1970-01-01 00:00:00 +0000
571+++ README.md 2015-12-19 07:36:54 +0000
572@@ -0,0 +1,26 @@
573+ReadMe - Ubuntu File Manager
574+============================
575+
576+Ubuntu File Manager App is the official file manager app for Ubuntu Touch. We follow an open
577+source model where the code is available to anyone to branch and hack on. The
578+ubuntu file manager app follows a test driven development (TDD) where tests are
579+written in parallel to feature implementation to help spot regressions easier.
580+
581+Dependencies
582+============
583+**DEPENDENCIES ARE NEEDED TO BE INSTALLED TO BUILD AND RUN THE APP**.
584+
585+A complete list of dependencies for the project can be found in filemanager-app/debian/control
586+
587+The following essential packages are also required to develop this app:
588+* [ubuntu-sdk](http://developer.ubuntu.com/start)
589+* intltool - run `sudo apt-get install intltool`
590+
591+Useful Links
592+============
593+Here are some useful links with regards to the File Manager App development.
594+
595+* [Home Page](https://developer.ubuntu.com/en/community/core-apps/file-manager/)
596+* [File Manager App Wiki](https://wiki.ubuntu.com/Touch/CoreApps/FileManager)
597+* [Project page](https://launchpad.net/ubuntu-filemanager-app)
598+
599
600=== removed file 'README.translations'
601--- README.translations 2014-08-16 07:04:04 +0000
602+++ README.translations 1970-01-01 00:00:00 +0000
603@@ -1,36 +0,0 @@
604-# Updating translations
605-
606-Translations for the Filemanager app happen in [Launchpad Translations][] and
607-are automatically committed daily on the trunk branch in the po/ folder.
608-
609-They are then built and installed as part of the package build, so that
610-developers don't really need to worry about them.
611-
612-However, there is one task that needs to be taken care of: exposing new
613-translatable messages to translators. So whenever you add new translatable
614-messages in the code, make sure to follow these steps:
615-
616- 1. Run click-buddy retaining the build directory:
617- `click-buddy --dir . --no-clean`
618- 2. Commit the generated .pot file: `bzr commit -m"Updated translation template"`
619- 3. Push the branch and send a merge proposal as usual
620-
621-And that's it, once the branch lands Launchpad should take care of all the rest!
622-
623-# Behind the scenes
624-
625-Behind the scenes, whenever the po/*.pot file (also known as translations template)
626-is committed to trunk Launchpad reads it and updates the translatable strings
627-exposed in the web UI. This will enable translators to work on the new strings.
628-The translations template contains all translatable strings that have been
629-extracted from the source code files.
630-
631-Launchpad will then store translations in its database and will commit them daily
632-in the form of textual po/*.po files to trunk. The PO files are also usually
633-referred to as the translations files. You'll find a translation file for each
634-language the app has got at least a translated message available for.
635-
636-Translations for core apps follow the standard [gettext format].
637-
638- [Launchpad Translations]: https://translations.launchpad.net/ubuntu-filemanager-app
639- [gettext format]: https://www.gnu.org/software/gettext/
640
641=== modified file 'debian/changelog'
642--- debian/changelog 2015-06-26 18:59:37 +0000
643+++ debian/changelog 2015-12-19 07:36:54 +0000
644@@ -1,3 +1,9 @@
645+ubuntu-filemanager-app (0.4ubuntu1) UNRELEASED; urgency=medium
646+
647+ * Improved READMEs
648+
649+ -- Girish Rawat <emailgirishrawat@gmail.com> Sat, 19 Dec 2015 13:03:56 +0530
650+
651 ubuntu-filemanager-app (0.4) wily; urgency=medium
652
653 * Renamed PAM module to not conflict with the Terminal one.

Subscribers

People subscribed via source and target branches