<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="Tiki CMS/Groupware via FeedCreator 1.7.2.1" -->
<?xml-stylesheet href="http://www.jollans.com/tiki/lib/rss/rss-style.css" type="text/css"?>
<?xml-stylesheet href="http://www.jollans.com/tiki/lib/rss/rss20.xsl" type="text/xsl"?>
<rss version="2.0">
    <channel>
        <title>Tiki RSS feed for forums</title>
        <description></description>
        <link>http://www.jollans.com/tiki/tiki-forums_rss.php?ver=2</link>
        <lastBuildDate>Wed, 08 Sep 2010 19:39:44 +0100</lastBuildDate>
        <generator>Tiki CMS/Groupware via FeedCreator 1.7.2.1</generator>
        <image>
            <url>http://www.jollans.com/tiki/img/tiki.jpg</url>
            <title>Multi-Language Software</title>
            <link>http://www.jollans.com/tiki/tiki-index.php</link>
            <description><![CDATA[Feed provided by Multi-Language Software. Click to visit.]]></description>
        </image>
        <language>en-us</language>
        <item>
            <title>Excel Export based on the translation status</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=587</link>
            <description><![CDATA[In version 4.7x.0035, there is a change to the Excel Export dialog.

Previously there was an option to export only "new, changed or untranslated" strings. The exact way that this worked was not really clear for users, and it was rather inflexible.

I have now replaced that option with a more general option to export texts with specific status values, as shown in the following screenshot.
{img src="img/wiki_up/ExcelExportForStatus.gif" }

This is still a bit confusing, because the status is defined for each translation, but the export is filtered on a line by line basis. A line will be written to the Excel file if any translation on the line has one of the specified status values.

By the way, this logic ignores the status of the text in the original language (which is normally ''original text'').

The logic in the previous version was equivalent to selecting all status values, except for ''Excel''. This was based on the idea that all translations should be made - or at least checked - by an external translator. In this case, the only reliable translations are ones which have been imported from Excel. I think that that was a reasonable approach for some users, but a bit too strict for others.

Phil]]></description>
            <author>Phil</author>
            <pubDate>Sun, 05 Sep 2010 22:23:06 +0100</pubDate>
        </item>
        <item>
            <title>Resource Compiler Mismatch</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=581</link>
            <description><![CDATA[Hi,

After scanning my project, some items on the source code tab have a mismatch between resource and compiler on the tooltip (hover the cursor over an item in the name column) eg...

Component: MDIForms.h
Property: BarManager.Items[0].Text
Resource: cmdOpen.Text
Compiler: cmdExport.Text

This results in the wrong text displaying in the app at run-time but I can't see any issues in the resx etc. Please help!

Thanks,
Paul]]></description>
            <author>sondex</author>
            <pubDate>Fri, 03 Sep 2010 14:22:11 +0100</pubDate>
        </item>
        <item>
            <title>export additional resources</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=579</link>
            <description><![CDATA[I have some problems by exporting my resources files to excel.

I mention that the additional resources are not included in my excel export.

How can I get an export of the additional resources?]]></description>
            <author>annschillewaert</author>
            <pubDate>Tue, 31 Aug 2010 13:28:22 +0100</pubDate>
        </item>
        <item>
            <title>TIP: Include Localized Files in MSI</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=574</link>
            <description><![CDATA[I was using MLS to translate a winform / Windows Forms Application and used several hours before I noticed the ressource files where not present in the install folder after I installed my program as it should be.

The localized files are not a part of the basic winforms project output.

If you are using an MSI as your installer, you have to add a project output for the winforms project of the type localized project.

I spend hours debugging and accused both Windows 7 and my PC to have bugs etc. But finaly I noticed the missing ressource files - bugger.. One of those erroer you just hate..

Phill -> You could consider update the guide for Windows Forms to include this scenario as this is the ".NET way of installing WinForms".. It would have help me and spared me for 1-2 hours work..]]></description>
            <author>nickniebling</author>
            <pubDate>Wed, 25 Aug 2010 13:58:18 +0100</pubDate>
        </item>
        <item>
            <title>Request: Localization of solution/several projects</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=571</link>
            <description><![CDATA[It would be nice to have a "solution scope" of localization! So MLS can control several projects at the same time!

We have several projects (10+) in a solution. Lets just say half of them (5+) has strings to be localized. Only 1 of the projects has a huge amount of strings (lets say 1.000) and the other projects only has a few (lets say less than 25).

With a "solution scope" of MLS, the MLString class is located in a project for itself, so import and export can be done through 1 project. I get that this is not always the usecase - but for some it is!

Today, we have to make a project to control localization for the "small projects" (25-), make a reference to this project manual and call our homemade MLString class where we place our strings for localization. Then we only have MLString in this project shared by "the small projects". The "large project" (1.000+) gets its own MLString and localization handling.

For us the "large project" is either a ASP.NET Website/Webapplication or a Windows Forms Application.

Hope you get the point and see the potential in letting the user choose between 2 scopes: project/solution.]]></description>
            <author>nickniebling</author>
            <pubDate>Tue, 24 Aug 2010 14:00:06 +0100</pubDate>
        </item>
        <item>
            <title>targetver and targetdir</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=570</link>
            <description><![CDATA[Hello every body,
I use the Add-in for .net 2008, version 4.71.0031
I create an example MFC MDI project with the appwizard with default options.
My original language is frensh.
With the Addin I add the english language respecting the "quick tour (Unmanaged C++ and MFC)", 2 subprojects en and fr-FR are created.
When I compile the project I have a lot of errors :
1 : TestMultiLangue_fr-FR : error PRJ0007 : Impossible de créer le répertoire de sortie 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\I:\Dev\TestMultiLangue\Debug\fr-FR'.
I remark that in the fr-FR project properties the TargetDir and targetPath link to the VS9 directory.

2 : i:\dev\testmultilangue\testmultilangue\mainfrm.cpp(71) : error C2653: 'LMultiLang' : n'est pas un nom de classe ni d'espace de noms
I have a lot of errors like this.

3 : i:\dev\testmultilangue\testmultilangue\mainfrm.cpp(71) : error C3861: 'ml_string' : identificateur introuvable
I have a lot of errors like this.

4 : i:\dev\testmultilangue\testmultilangue\propertieswnd.cpp(215) : error C2440: 'initialisation' : impossible de convertir de 'const CString' en 'TCHAR []'

5 : Other problem : The file targetver.h is not copied in the "en or fr-FR" directory.

Where is my error ?
think for replay]]></description>
            <author>tazer</author>
            <pubDate>Tue, 17 Aug 2010 09:41:46 +0100</pubDate>
        </item>
        <item>
            <title>how does it work for final user? </title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=566</link>
            <description><![CDATA[Hi all, Im interested in this tool, but just a simple question:

The final user got the .exe and if he wants to add a new languaje, then just create a new .XML and store it into a folder, and the .exe will recognize the new languaje without a rebuild ???

TIA.]]></description>
            <author>LuisMX</author>
            <pubDate>Mon, 02 Aug 2010 14:45:35 +0100</pubDate>
        </item>
        <item>
            <title>MFC Support that works - Satellite DLLs</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=563</link>
            <description><![CDATA[Actually, the previous support for MFC (unmanaged C++) projects in the Add-In worked, but it had a serious downside. 

There is no easy way to get MFC to load resources in a specific language. The only reliable way is to add extra code to more or less every class which will load resources. The Add-In's help file describes a lot of specific ways to do this for different MFC classes. It's not pretty.

Now I have discovered that newer versions of MFC have support for satellite DLLs. In version 4.7x.0028 I have added support for MFC satellite DLLs. Finally, this is now MFC support which simply works without having to add lots of extra code by hand.

I have tried to describe it in ((MfcSatelliteDlls|this article)), which you can also access via the Articles menu item. I have also updated the ((MultilangVsNetQuickTourMfc|''Quick tour'')) to refer to MFC satellite DLLs. Unfortunately, it is anything but quick.

Next on the list, is the help file.(:smile:)

Phil]]></description>
            <author>Phil</author>
            <pubDate>Sun, 18 Jul 2010 20:53:05 +0100</pubDate>
        </item>
        <item>
            <title>The Square Root of Three</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=4&amp;comments_parentId=555</link>
            <description><![CDATA[I fear that I will always be
A lonely number like root three
The three is all that's great and right
Why must my three keep out of sight
Beneath the vicious square root sign
I wish instead I were a nine
For nine could thwart this evil trick,
with just a quick arithmetic
I know I'll never see a sum, as 1.7321
Such as my reality, a sad irrationality
When hark! What is this I see,
Another square root of a three
Has quietly come waltzing by
Together now we multiply
To form a number we prefer,
Rejoicing as an integer
We break free from our mortal bonds
With the wave of magic wands
Our square root signs become unglued
The love for me has been renewed

[http://www.casino-spielen.biz/|casino deutschland]]]></description>
            <author>SophiaGreen</author>
            <pubDate>Thu, 01 Jul 2010 19:58:24 +0100</pubDate>
        </item>
        <item>
            <title>Using the same text on multiple forms's controls and/or projects</title>
            <link>http://www.jollans.com/tiki/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=553</link>
            <description><![CDATA[Hi,
we have a large project where a lot of controls must display the same text on multiple forms.
These forms could belong to different projects.
For example we have a button with the text "Cancell" that is placed on a lot of forms and these forms are used on a lot of projects.
Is there a way to avoid to translate this text "Cancel" dozen of times ???
Thanks a lot
Stefano]]></description>
            <author>delfo</author>
            <pubDate>Mon, 28 Jun 2010 08:07:00 +0100</pubDate>
        </item>
    </channel>
</rss>
