Ryzom

Status report N2 (Monday, 30th May, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- described translation pipeline usage in Web Translation Tool for string files
- created database and setup CakePHP application with prototype page layout for it

What is planned for the current week.
- finish importing generated diffs into database (for strings, phrases and sheets)
- making translations page, where translators can make their suggestions, and vote for translations

Status report N3 (Monday, 6th June, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- importing diff files generated by translation pipeline - only strings file (no user interface yet)
- reworked pages layout for better navigation (not all pages rebuilded yet)

What was not accomplished that was planned.
- importing other diff file types (phrases, sheets)
- it's possible to add translations, but translation page is not yet completed

What is planned for the current week.
- finish importing generated diff files into database (phrase files and sheet files)
- finish translations page, where translators can make their suggestions, and vote for translations
- make basic exporter for string diff files from database back to files that can be used by translation_pipeline

Status report N4 (Monday, 13th June, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- further Ryzom translation pipeline integration
-- translation pipeline on linux: translation_tool binary compiled on linux and ported some .bat scripts to bash
-- created RawFile datasource in CakePHP (it's able to list translation files in translation pipeline directory on filesystem and parse translation files) with import/export handling in controller
-- RawFile view with file details and content
-- frontend to import translation files from pipeline
- parser for phrase files, necessary database and design adjustments
- basic exporter for strings .uxt files (for diff files in database) back to files that can be used by translation pipeline
- more work on layout (all pages moved to new look)
- work began on administrator tools page

What was not accomplished that was planned and why.
- importing sheets files into database
- users can add translations and vote on them, but can't comment yet

Integration with Ryzom translation pipeline takes more time than i thought at start.

What is planned for the current week.
- sheets parser and database adjustments for this file type
- continue to work on translation page for users (including translation comments)

What risks are there for the current week.
I will have less time this week, because i have two exams this weekend at school, but i plan to finish objectives for this week.

Status report N5 (Monday, 20th June, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- Added comments (in database, model file, controller file, view files and modified other views to support it)
- Fixed many parser bugs

What was not accomplished that was planned and why.
- importing sheets files into database

Due to school commitments and fixing other parser bugs i didn't have time to finish this task.

What is planned for the current week.
- futher work on translation files parser (including sheets files)
- translations exporter back to translation pipeline (phrase and sheets files)

What risks are there for the current week.
I have a few exams this weekend, so again my time for the project is limited.

Status report N6 (Monday, 27th June, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- Fixed more parser bugs.
- Minor layout adjustments.

What was not accomplished that was planned and why.
- importing sheets files into database
- translations exporter back to translation pipeline (phrase and sheets files)

I've had a few exams this weekend, so my time for the project was limited.
Exams are over now, so i can spend more time with the project.

What is planned for the current week.
- futher work on translation files parser (sheets files)
- translations exporter back to translation pipeline (phrase and sheets files)
- frontend to exporter (accepting translators suggestions)
- creating authorization module
- split view templates into commonly used element templates that can be used in many view templates

What risks are there for the current week.
None.

Status report N7 (Monday, 4th July, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- Auth module: added login page, basic user registration with activation by admin, more info on users, permissions for admin pages and users pages
- sheets parser, but without import into database yet
- translations exporter back to translation pipeline (phrase files)
- frontend to exporter (with possibility to choose translations for export)
- added translation_files table in database and changed importer process respectively. identifiers belongs to translation_file now (instead of language), because they don't have to be unique between files

What was not accomplished that was planned and why.
- split view templates into commonly used element templates that can be used in many view templates
- importing sheets into database

Due to some database redesign i left it for later.

What is planned for the current week.
- improving user registration (sending email with confirmation link)
- importing parsed sheets into database
- exporter for translated sheets
- database redesign for global identifiers
- at the end of this week i want to be able to import all Ryzom translation files, generated diff files, and export translation back to these files

What risks are there for the current week.
None.

Status report N8 (Monday, 11th July, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- module for import parsed sheets into database
- exporter for translated sheets
- improved user registration (sending email with confirmation link)
- successfully imported ryzom translated and diff main files (strings, phrases, sheets) into database and exported them back to files with proper syntax for translation pipeline

What was not accomplished that was planned and why.
- database redesign for global identifiers
I didn't figure out yet what to do with different sheets (columns) for each language. I need to think again if it's good idea.

What is planned for the current week.
- improve authorization module
- allow only activated (by admin) users to sign in
- change controllers to insert into db for associated models actual user id instead of TestUser
- improve translation page
- add "save and move to next (translation)" function
- add neighbour identifiers to the left menu in view/add/edit translation
- sheets translation view
- add content_description field to identifiers
- make reference_string as default translation in .new translation. view
- improve layout
- add "register" and "logout" links in layout
- improve import
- add checking for type of import file (phrase diff with // DIFF_VERSION, sheet with DIFF_COMMAND 1st column etc). Now it's done by filename.

What risks are there for the current week.
None.

Status report N9 (Monday, 18th July, 2011) (Web Translation Tool)

What was accomplished in the previous week.
- improved authorization module
- allow only activated (by admin) and confirmed accounts to sign in
- changed controllers and views to insert into db for associated models actual user id instead of TestUser
- improved translation page
- added "save and move to next (translation)" function
- added neighbour identifiers to the left menu in view/add/edit translation
- crated sheets translation view
- added content_description field to identifiers
- made reference_string as default translation in "new translation" view
- improved layout
- added "register" and "logout" links in layout

What was not accomplished that was planned and why.
- add checking for type of import file (phrase diff with // DIFF_VERSION, sheet with DIFF_COMMAND 1st column etc). Now it's done by filename.
I will do it later along with file charset checking.

What is planned for the current week.
- making WebIG interface for players to make translation suggestions
- add indexes on foreign keys in database to speedup popular queries

What risks are there for the current week.
None.