Page Comparison

Beebox Server 1.02.69, December 9, 2016

New features:

• File delivery: The target files are now correctly marked as "Ready" and not stuck on "Translated" when the source file (but not the text) have changed after the translation.

Beebox Server 1.02.68, November 18, 2016

New features:

• Dita files: The markup is now properly shown in the Wordbee editor when "Hide markup preceeding and trailing text" option is unticked.

Beebox Live Preview 1.01.26, October 27, 2016

Fixes:

• URL replacement: Absolute URLs in the previewed page where not adjusted. When such a link was clicked by the user, the navigator left the preview site. This is now fixed.

Beebox Server 1.02.67, October 27, 2016

New features:

• Instruction file - Validation of languages: Beebox now checks if the locales in the instructions file are valid. If not, an error is shown.
• Pass through projects and meta information: Meta information stored in instructions files are now transferred into Wordbee as comments for both regular and pass through projects. Also see here.
• New Beebox extension type: You can now add "daemon" process extensions to Beebox. These are run every 1 minute. Such an extension can e.g. scan a folder or database for new content and push the content into a Beebox project. This can include transforming files before dropping them into a Beebox project.

Beebox Server 1.02.66, October 4, 2016

New features:

• Callback: The Pass Through project callbacks now contain the details information, including the filenames of the translated files.
• Other: Includes all improvements made for Wordbee Translator on CSV files since the last Beebox release.

Beebox Live Preview 1.01.25, October 4, 2016

New features:

• Proxy configuration options: Better support in setups where a proxy server is placed in front of Live Preview.
  The use of a proxy server is useful if you want to make live preview accessible with a custom domain name and without exposing the Live Preview site directly to the Internet. A couple of new configuration options support almost any setup.

Beebox Server 1.02.65, September 20, 2016

New features:

• Upload XLIFF to jobs: The XLIFF import has been fixed to avoid loosing translations when editing project settings right after the import.

Beebox Server 1.02.64, September 13, 2016

New features:

• Smoother integration with Beebox Live Preview: Clicking the "Preview" link in the translation editor of Wordbee Translator now opens the Live Preview site directly. This feature requires that you install Live Preview on the Beebox server and that you enable live previewing in the Beebox project (see Project > Settings > Language Provider).

• Language codes: Change of language code "no-no" to the ISO compliant "no-NO"

• Other: Includes all improvements made for Wordbee Translator on text filters since the last Beebox release.

Beebox Live Preview 1.01.24, September 13, 2016

New features:

• URL adjustment: Absolute hyperlinks are adjusted so that you can click any link in the preview and you stay within the site.

Beebox Server 1.02.63, August 22, 2016

New features:

• DITA filter: New configuration option to hide away untranslatable inline content. In DITA you may apply this to the <codeph>. The untranslatable inline content is rendered as markup.

Beebox Server 1.02.62, August 10, 2016

New features:

• Segmentation rules: German segmentation rules extended to account for non-breaks at "... 10.Mal ..." and "... 10. Februar ..." and similar

Beebox Server 1.02.61, July 28, 2016

New features:

• Show CMS connector details: If a CMS is linked to the Beebox, the project dashboard will now display the connector name and version number. Example:

Image Removed  

The information is updated every time and a few minutes after the connector "talks" to the Beebox. It tells you which version of the connector is installed in the CMS. This is useful if you want to know whether your customer is using the latest version.

Beebox Server 1.02.60, June 28, 2016

New features:

• Segment length constraints: Beebox now fully supports assigning minimum and maximum translation length limits. How limits are assigned is specified in the text filters (which you typically configure using Wordbee Translator under the Settings section). Also see this announcement which shows the new filter configuration options: https://wordbee.zendesk.com/hc/en-us/articles/221709907-Apply-Text-Length-limits-to-files-independent-of-segmentation . Advanced features are available for multilingual Excels: Apply limits to specific columns, read-out limits from Excel columns, etc.
  Limits are shown in the Beebox translation editor. Translation jobs include limits both as custom attributes in XLIFF jobs and when exporting work to Wordbee Translator.  

Beebox Live Preview 1.01.23, June 10, 2016 (BETA LAUNCH)

Beebox Server 1.02.58, June 9, 2016

Great news! This is the initial release of Beebox Live Preview - BETA.

Beebox Live Preview is an add on to Beebox Server that lets you preview CMSes, static and dynamic web sites while you translate.

Translators view their translations with the exact layout and rendering of the final web site. Run the install on the same server as your Beebox Server.

Live Preview information

Beebox Server 1.02.58, June 2, 2016

New features:

• Preview translated CMS content: When using Beebox to translate CMSes, it can now provide real-time previews of the translated pages by means of the Beebox Live Preview add-on. This feature is still beta. If you are interested in more information please contact Wordbee.

Bug fixes:

• Multilingual CSV files: A bug prevented from translating multilingual CSV files (it worked well with monolingual CSV files).

Beebox Server 1.02.55, May 19, 2016

New features:

• DITA files and encoding: Entity references contained in DITA files are now converted to the actual print characters. 

• Open Wordbee project and jobs from Beebox: We added hyperlinks to directly navigate from a Beebox project to the Wordbee Translator project, if such a link was created.
  • You can navigate to the project from "Settings" > "Translation vendor"
  • You can open a job in Wordbee Translator from "Translation" > choose a job > click the "Open at vendor" link.

• Faster multilingual file processing: The generation of translated multilingual files (available for XML, JSON, EXCEL and CSV) has been optimized. Instead of creating the file individually per target language, it is created only once with all language translations. This change now means that a multilingual file is auto-created only once all translations into all languages are available and approved.

• Customize text extraction rules individually per file: Similarly to adding an "instructions" file with a source file you can now optionally add special text extraction rules with each source file. In that case the custom rules will be used for processing the file and not the ones configured in the project settings. Read more.

Bug fixes:

• API methods: Deleting "sandbox": The api/files/directory?token=&locale=sandbox method may lead to deletion of the sandbox parent directory itself. This has been fixed.

• Display of right to left languages: A bug with rendering markup for right-to-left languages was fixed. Markup is now properly rendered for languages such as Hebrew or Arabic.

Beebox Server 1.02.52, May 6, 2016

New features:

• Customize job names from meta data: Beebox always did let you customize job names to a limited extent (choice of prefix). It is now possible to name jobs from file level meta data. Imagine that each source files includes the client name. Now you want to create a job that combines all new content from this client and you want the client name be part of the job name! This is now possible in two steps:
  • Include the client name (or other meta information) with each file or more generally on folder level. (e.g. assign client name and urgency to files or folders)
  • Define how content shall be grouped into jobs (e.g. by client name and urgency)
  • Define if the job name shall include the meta information (e.g. the client name and urgency)

Start reading here: Job content grouping

• Disregard files which names start with ~ (tilde): These files often are temporary files in the Microsoft world. Following multiple feedback from customers we now automatically exclude such files from translation.

Beebox Server 1.02.51, May 3, 2016

New features:

• Pass-through projects and delivery folder: It is now possible to optionally transfer translated files into the "in" directory. This can be configured in the Hotfolder settings, see PT - Settings - Hot folders . Note that this feature had already been available with regular projects.

Image Removed

• Auto correct markup in translations: The "Actions" popup in the Beebox translation editor now includes a tool to find and fix incorrectly placed markup. See http://documents.wordbee.com/x/KpUX

Image Removed

• XLIFF containing invalid characters: Invalid control characters (such as 0x03) contained in XLIFF files made processing fail. The filter now disregards characters not permitted by the XML 1.1 standard. This error specifically affected Drupal users. It seems that when using the CKEditor, there are situations where the ASCII 3 character was inserted into the text.

Fixes:

• Creating CMS Wordpress projects: When creating new CMS projects and leaving the default "Wordpress" selection, the system actually created an Adobe AEM project.

Image Removed

• Beebox translation editor action shows error: When machine translating content using the "Actions" popup in the Beebox editor, an error message was displayed at the end (even though no error occurred). This has been fixed.

Beebox Server 1.02.48, April 26, 2016

Bug fixes:

• Manual upload of XLIFF to job: In certain circumstances, uploading a translated XLIFF file to a job made the import dialog stop working.

Minor changes:

• Instructions files and language codes: When reading ".beebox" instructions files, language codes no longer need to match case sensitive. Inputting "ja-jp" is now accepted in place of "ja-JP".

Beebox Server 1.02.47, April 21, 2016

New features:

• Performance enhancement: Processing very large files (such as 60 MB + xml files) is now 15% to 20% faster.

Minor changes:

• XML and invalid characters: Characters not allowed in XML files are disregarded and no longer lead to errors.

Bug fixes:

• Multilingual XML using untranslatable terms: In certain circumstances and when using the untranslatable terms feature (replacing terms by markup) an error may occur: Markup of the terms may be restored incorrectly in translated files.

Beebox Server 1.02.42, February 9, 2016

New features:

• Hot folders: Each project can now be configured to expose one or more hot folders. Per hot folder you can specify into which language(s) content is translated. This makes it very convenient to propose language aware folders to customers or IT systems to submit content. To access this feature go to "Settings" and then Hot folders:

Image Removed

This feature is also great to connect with a client over Dropbox, Box.com, Google Drive, FTP or any other file sharing mechanism. Also see Beebox Cloud Storage connectors.

• Cloud and FTP delivery: Translated files are saved in the project "out" directory. Beebox now proposes an option to (a) rename files e.g. by appending the language code and (b) to transfer translations back to the project "in" directory. The latter option is specifically interesting in FTP or Cloud sharing scenarios because you then only need to share the "in" directory to both receive and deliver files. To access this feature go to "Settings" and then Hot folders:

Image Removed

• Autorun - Approve translations - Change: The following Automation option was extended. Until now it did not apply to jobs in status "Work finished", i.e. when Beebox detected that work was done in the TMS. From now on, it will also process these jobs by approving content, applying translations to the project and closing the job.

Image Removed

Fixes:

• .properties files and HTML: A minor bug with HTML embedded in properties files was fixed. If the HTML contained translatable attributes (such as "title="), the attributes did not get translated.

Beebox Server 1.02.39, January 27, 2016

Fixes:

• Wordpress and Drupal CMS: A bug was introduced in an early January Beebox release for processing Wordpress and Drupal content. This release fixes the bug.

Beebox Server 1.02.38, January 18, 2016

New features:

• Costing individually per language: If you choose to have Beebox cost translation work, you are now able to optionally set prices individually per target language in the project settings:

Image Removed

• Cloud sharing and FTP file translation: You can now more easily connect a Beebox project to Dropbox, Box, Google Drive and other systems. Instead of sending files by email, you can receive them via the cloud and kick off translation workflows automatically. Read more.

• Group content of jobs by folder or extension: This is useful if you want each job contain segments/files from the same location or having the same file extensions. The assigned job reference can be customized to include shared folder or extension. See the project settings page and scroll down to the jobs related section.

Image Removed

Beebox Server 1.02.37, January 13, 2016

New features:

• Signed setup program: The setup file is now cryptographically signed for Wordbee S.A. Downloading and running the installation program no longer shows warnings from anti viruses or browsers.

Fixes:

• Multilingual XML files: Can now be processed with the Beebox.

Beebox Server 1.02.33, January 5, 2016

New features:

• SDL LiveContent: The project creation wizard can now create projects for SDL LiveContent (in conjunction with the Wordbee connector for SDL LiveContent).

Fixes:

• Windows 2012 R2: The Beebox installation failed in certain configurations.

Beebox Server 1.02.32, December 28, 2015

New features:

• Pass through projects: When removing a source file when the translation was already finished (status "Done"), the workflow is no longer cancelled. Now, cancellation only takes place in Beebox and Wordbee Translator while a workflow is still unfinished. Also see: PT - What happens if I remove source files from the project?

Beebox Server 1.02.30, December 17, 2015

New features:

• CMS API: The api/actions/action method is now available to connectors using standard API credentials.

Beebox Server 1.02.29, November 30, 2015

New features:

• New cancellation workflows in regular projects: Improved cancellation workflows when Beebox is connected to a TMS. When you cancel a translation job in Beebox which was already sent to a TMS, the new options will cancel the job in the TMS as well. The options are accessible in the Automation settings (see bottom of this page).
• Use of Wordbee Translator: Job cancelled in Beebox => Job automatically cancelled in Wordbee Translator
• Use of other TMS: Job cancelled in Beebox => XLIFF file is removed from the TMS hotfolder. 
   

• Meta information in instructions files: Addition of file-level meta information in instructions files. Before, Beebox permits to set segment-level information only. File level information may be the URL of a web page, job instructions or any other data that shall be sent to the translation team. This information is transferred to the TMS (translation team) inside XLIFF or Wordbee Translator jobs, depending on which TMS you are using.
   

• Display of meta information: File-level meta properties are easily accessible in various places of the user interface:
  Image Removed 

Fixes:

• Client emails in pass-through projects: Delivery of final translated files did not trigger the client email notification.
• Save project settings: The "Text alignment" and the "Preliminary translations" options in the project settings page got reset whenever you edited the Automation settings.

Beebox Server 1.02.27, November 19, 2015

Fixes:

• Translation editor may not show: The translation editor may stay blank in some cases where segments are included in an open translation job. This bug was introduced in a September 2015 release.

Beebox Server 1.02.26, November 18, 2015

New features:

• Pass-Through projects:  A new project type that works in combination with Wordbee Translator. Any files saved/sent to the Beebox will be handed through to Wordbee Translator. No text-extraction or pretranslation takes place inside the Beebox. Upon completion of work by the translation teams, translated files are retrieved back into the Beebox for delivery to a file directory, file sharing system, the API or a CMS. For more information see:
  • Project Types
  • Add Pass-Through Project
  • View Pass-Through Project

• Relaxed behavior with invalid instructions files: When you placed a malformed instructions file into the Beebox "in" directory, access to the project from the user interface was no longer possible until you fixed the error. This has been changed now.

Fixes:

• Case of loss of last changes: We identified a case where editing project settings could make the Beebox "forget" the most recent changes to the project memory or job status. This could happen if settings were edited immediately after automatic operations were executed.

Beebox Server 1.02.25, November 9, 2015

Fixes:

• Create deliverables button: There was a bug with the first option in "Create deliverables" in the "Target files" page. The first option did not create just those files that can be delivered (translated and approved content) but all files. If you are usig this functionality then please upgrade.

Image Removed

Beebox Server 1.02.23, October 22, 2015

New features:

• File preview in Wordbee Translator: Translators can now preview Beebox files from within the Wordbee translation editor. Click a segment in the editor and then preview from the Document viewer panel. The Beebox administrator must explicitly enable this feature, see: Settings - Translation Vendor. Preview/Download works for the original and translated files.
   
• New pseudo-translation algorithm: Convert all characters to "*". This algorithm makes it very simple to verify if all translatable text was extracted from the source files.
   
• Find your Beebox URL: When you connect CMS systems to your Beebox you need to supply the publicly accessible URL of your Beebox. We added a new tool to find out this URL and verify if your Beebox is accessible in the Internet. See: Public Beebox URL
   
• Contextual help: The help link in the Beebox now systematically opens the relevant help documentation.

Version 1.02.22, October 7, 2015

Fixes:

• DITA files: A bug with processing DITA files is corrected.
   
• Wordbee Translator timeouts: When sending very big translation jobs into Wordbee Translator the operation may exceed a maximum transfer time-limit. This limit is now extended.

Version 1.02.19, September 21, 2015

New features:

• Job context size configurable between 0, 1 and 5: You can now choose how much text before and after each segment shall be included with a job. Before you had the choice of 0 or 1 segment. This is now extended to up to 5 segments before and after. In most cases, a context size of 1 segment before and after is however sufficient for a translator or revisor. The context size is configured in the Project Settings page:

Image Removed

Version 1.02.18, September 14, 2015

New features:

• Job information in editor: When viewing segments of one or all files (use Quick Search link in a project), the Beebox now shows which segments are contained in a job. Clicking the icon display the job reference:

Image Removed

• Job shows source files list: The job details page now shows which source files have segments included in the job. This is useful if you want to immediately see the source files contained in a job (before, you could see this only when viewing the job segments):

Navigate to a job and click the Content tab. At the bottom you will find the list of source files:

Image Removed

• "unapproveAll" flag in instructions file: The instructions file now supports the "unapproveAll" boolean flag. This feature is, for example, used by the Joomla connector to force resending previously translated and approved content once again to the TMS or translation team. A Joomla user would tick the option if he/she feels that the translations require improvement.

• Unlinking Wordbee connection: Unlinking a Beebox project from Wordbee (Settings > Translation Vendor) now shows an error if there are still open jobs in the project.

Version 1.02.16, September 2, 2015

New features:

• Contextual help added to "Administration" and "Account & License" pages. Clicking "Help" directs you to the corresponding help section.
• Enabling/Disabling automation page: When re-enabling automation, a new option lets you restore the previous settings. Before, you always had to choose from a list of presets.

Bug fixes:

• The project Automation page did not permit to choose pseudo translation modes "Reshuffle and change length" algorithms.

Version 1.02.15, August 24, 2015

Bug fixes:

• XLIFF jobs are now fully XLIFF compliant (xliff namespace added, file/header/tool node added, occasional zero padding at end of file removed).
• Download of editor search results to XLIFF failed for untranslated segments.

Version 1.02.14, August 7, 2015

New features:

• Translation editor - New download options: There is a new link to download filtered segments to JSON or XLIFF straight from the translation editor. Click here for more.
• Translation editor - Actions link moved: We have moved the "Actions" link to batch change filtered segments to the navigation pane (it was in the top right of the page before).
• Help link added: We added a link to each page to access the user guide.

Version 1.02.13, August 3, 2015

New features:

• Project creation wizard improved: When you create a new project you can now immediately preset a workflow. This removes a lot of manual configuration steps.
• Project Automation settings page: Presentation and editing of the automation settings page is enhanced.

Version 1.02.12, July 30, 2015

New features:

• CMS project creation wizard: CMS translation projects can now be created with a simple wizard. Click "New project" and chose option to create a CMS translation project. This new wizard makes creating CMS projects a breeze.
• Dashboard enhancements: The top block of the dashboard now shows more relevant information such as CMS and TMS details.
• Kentico connector: The default Kentico configuration was changed to exclude hyperlinks from the translation process.

Bug fixes:

• When sending content via the API, temporary files are created in the Windows temp directory but not deleted automatically.

Version 1.02.09, July 27, 2015

New features:

• Project folder naming When creating a new project you can now have the project directory be named like the project name. There is a new option. By default, the directory name will still be the unique alphanumeric project ID.
• SRX custom rules When installing custom segmentation rules (.srx files) you do not need to restart the Beebox Windows service anymore. It is sufficient to reset the server in the UI. Go to "Administration" and click "Reset server".
• XLIFF language handling The Beebox now accepts XLIFF files that lack the source and target language attributes. If these are omitted then the Beebox presumes the project source language and the first of the project target languages.

Version 1.02.08, July 23, 2015

Bug fixes:

• When manually exporting and importing xliff jobs, the import could fail in certain cases because the system assigned wrong segment IDs.

Version 1.02.06, July 10, 2015

New features:

• Auto-signed certificates are now accepted. This lets you access the Beebox using SSL without having to buy a certificate from a certification authority. Create an auto-assigned certificate in IIS, then assign to the Beebox web site.

Version 1.02.04, June 28, 2015

Bug fixes:

• Beebox extension feature: The sample extensions contained a bug. This may cause failures of automatic operations in the previous 1.02.01 release. Please upgrade. Job names in Wordbee Translator displayed internal ID intead of Beebox job name. Fixes a problem with aligning Word and Excel files.

Version 1.02.01, June 22, 2015

New features:

• Multilingual jobs (BETA) By default the Beebox creates bilingual jobs with one source language and a single target language. We have added a new option to create jobs into multiple languages. The Beebox creates such jobs for untranslated or unapproved content in all languages where there are untranslated or unapproved contents. It attempts to align source segment and translations in the different languages. NOTE: Currently such jobs can be exchanged using XLIFF (one file per target language) but not with Wordbee Translator.
• Microsoft.Net extensions The Beebox lets users develop c# or VB.Net code and upload to the Beebox. Add custom filters, custom pseudo translation algorithms, algorithms renaming/copying translated files and more. For more information go here.

Version 1.01.0062, May 29, 2015

New features:

• Delete project data in one step: Below a project's left navigation menu you find a new "Maintenance" link. The maintenance page lets you delete all project files easily: Delete source and target files, delete all jobs, delete all project memory content. Cleaning a project can be very useful during testing. Though, it should not be used with production projects.

Version 1.01.0061, May 28, 2015

New features:

• Automatically remove old files: A new option was added under "Settings" - "Automation". If enabled it automatically removes source and target files that are older than a customizable number of months. Enabling this option reduces both disk space usage and enhances performance. Translations of these files in the project memory are not removed.
• Customizable segmentation rules: You can now upload your own SRX files if the default rules in the Beebox do not match your specific requirements. See the Beebox "Administration" page for more details.
• New language codes: We added support for a few "unofficial" languages: en-AR (English Argentina), en-MEA (English Middle East and Africa) and fr-MEA (French Middle East and Africa).