17 OCT 2024 - Welcome Back to TorrentFunk! Get your pirate hat back out. Streaming is dying and torrents are the new trend. Account Registration works again and so do Torrent Uploads. We invite you all to start uploading torrents again!
TranSolution is a powerful and advanced application designed to integrate into Visual Studio and extract all ".resx" strings from any .NET solution, storing them in a single file that translators can localize.The same add-in is then used to import the strings back into the programmer's solution. Extremely easy to use with almost no learning curve. Includes extensive functionality such as the ability for translators to view your Windows forms and user controls during the translation process. Translators can even adjust the size and/or location of a form's controls to accommodate different sized strings (assuming permission to do so is granted by the programmers when the translation file is created). Includes many safeguards such as the enforcement of composite formatting items in all translated strings (e.g., ensuring your translator includes "{0}" when translating a string like "File {0} not found"). Also conducts extensive checking during incoming translation, logging all translation changes to the Visual Studio output Window and even warning the programmer about any conflicts (e.g., whether a string was changed by the programmer since outgoing translation - the programmer can then ignore the incoming string if required). This program genuinely makes translation about as easy as it can be for both programmers and translators.TranSolution main features:Extremely easy to use with almost no learning curve. WYSIWYG.Developer's version integrates right into Microsoft Visual Studio 2010, 2008 or 2005. Appears as a new item ("Translate") on the existing "Tools" menu. Just choose "Outgoing" or "Incoming" and you're on your way.In Visual Studio, use "Tools -> Translate -> Outgoing" which scans your Visual Studio .NET solution and bundles all strings into a single file for shipping to your translator. Your translator can then translate the file. When the file is returned, simply import it back into your solution using "Tools -> Translate -> Incoming". This completes the translation of your application.Programmers can select any target languages for the translationProgrammers can include or exclude any ".resx" file(s) they wish from the translation. "Resgen.exe" compatible ".txt" files are also supported.Translators can (optionally) view any forms in your application using the "Form View" option and translate the strings in this environment, similar to design view in Visual Studio itself (but restricted to only those properties that translators need to change - "Text", "Size" and "Location" - see next item just below)Programmers can optionally allow the translator to adjust the "Size" and/or "Location" of form-based controls in the "Form View" window (to accomodate small changes that may be required to fit strings of varying length). Programmers can also optionally restrict these changes to the default language form only if they wish (meaning that the translator can adjust the size and/or location of controls on the default language form only - translators won't be able to modify them for specific languages since they'll be inherited from the default language form)Programmers can optionally prevent translators from modifying strings that have already been translated. These will be read-only for the translator.Programmers need not explicitly turn on the "Localizable" property for every Windows form in their solution (which is required by Visual Studio to support Windows form localization). TranSolution will detect these and automate the process on request.Translators are forced to respect "composite format" string arguments, e.g., if the string "File {0} not found" is being translated, the translator will be forced to include the "{0}" in all translated stringsTranslators are forced to respect access keys (AKA hot keys or accelerator keys), e.g., if a control string labelled "&Next" is being translated (which appears to the end user as "Next"), the translator will be forced to include an '&' in all translated strings (and is warned if another control on the form contains the same access key)Translators can optionally copy duplicate strings to other rows automatically, e.g., if the string "Cancel" is translated on a given row, its translation will automatically be propagated to all other rows that also contain the string "Cancel" (ensuring consistent translations for duplicate strings)Translators can export one or more languages to another file if they need to parcel the work out to other translators (which can be imported back into the main file later)Translators can hide one or more language columns so they can focus on selected languages only (typically one language at a time)Translators can hide rows that have been completely translated so they can focus on only those (incomplete) rows that remainTranslators can conduct advanced string searches including regular expression searches. Searches may be confined to a single language column only or conducted column-by-column (down and across) or row-by-row (across and down). Searches can also be flagged to ignore access key ampersands (e.g., searching for "Next" will locate cells that also contain "N&ext").Tool tip in the main translation window displays the origin of each string (by pausing the mouse in the far left-hand column).During incoming translation, programmers are notified of any important issues including changes the programmer might have made to any existing strings since outgoing translation (which therefore no longer match what was translated). Other alerts will also notify the programmer of new strings that were added since outgoing translation (hence there will be no translation for them), strings that the translator neglected to translate, projects or files that are no longer in the solution (but were originally shipped for translation), etc.A complete record of all translation changes is written to the Visual Studio Output window during incoming translationComprehensive online helpDeveloped exclusively using Microsoft tools only. We believe this ensures greater stability by not relying on potentially unstable 3rd-party code.TranSolution requirements:Net framework 2.0 or laterTranSolution limitations:You will only be able to translate 10% of the strings in your solution
