[Mono-devel-list] [PATCH] Reworked unified Locale classes

[Ben Maurer]

On Tue, 2005-06-14 at 19:45 -0600, Peter Dennis Bartok wrote:
> Moving Locale.cs and MonoTODO.cs into a common area will break standalone 
> VS.Net projects. Several of the MWF contributors as well as Jordi and I use 
> those. I would like to keep MWF self-contained.

Since when has vs.net had issues with relative paths?

Chances are, something like:

                <File
                    RelPath = "../../build/common/Locale.cs"
                    SubType = "Code"
                    BuildAction = "Compile"
                />


                <File
                    RelPath = "../../build/common/MonoTODOAttribute.cs"
                    SubType = "Code"
                    BuildAction = "Compile"
                />

will fix it. Otherwise, you can always have a makefile target that will
copy the files if it is on a windows box or something. If we are going
to have a serious i18n framework, it's going to be extremely painful to
force people to copy and paste the code like that.


BTW, I had no idea what to do with locale.cs in MWF. There are stubs for
a bit of i18n, but that should probably get folded into whatever shared
framework we have. But there is a GetResource method that returns object
that I have no idea what it will do. For now, I didn't use the new
Locale.cs...

-- Ben