Issue 21783

I will add other later

update with more new Issue

Update again with Start Issue

Wow.  That's quite a list.  Thanks, utomo!  

Shouldn't we set the target milestone to 2.0 on this tracking bug,
since it's more or less the list of MS interoperability problems
we want to see fixed in OOo 2.0?

what's the advantage of such a bug over a query for the "ms_interop"
keyword?

Besides this: Looking at the dependency tree I see *a lot* of issues
which definately are *not* ms_interop (I don't even start to name them
here, there are too much of them). I spent half an hour to remove only
the wrong dependencies to issues which I'm involved with ... :(

the advantage of such a bug over a query for the "ms_interop"
keyword is: if we can reduce it til minimum, MS Office user will be
able to move to OOo/SO with minimum problem. 
as long as this issue still many, many MS Office user will facing
problem when they move from MSO to OOo. If they have big problem,
maybe they will not continue it. or if they propose the OOo/SO
migration to their company/organization/school, ETC. and they got a
lot of this kind of problem they will not be able to promote OOo/SO
anymore, even when the OOo/SO is better compatibility. and this can
meke bad image. 
but if this kind of Issue is minimum, people will  less facing problem
for migrating to OOo/SO. 

Maybe some Issue is not correctly placed in this Issue, because I use
dan kegels query for collecting this. and I hope other member will
add/correct it too. Thanks for correcting it. 
 
about the target I dont know if we can set it to 2.0 or not, but I
hope we can have it at 2.0. 

Please think before you write such statements:

The advantage of having a query for ms_interop is that if we can
reduce it til minimum, MS Office user will be able to move to OOo/SO
with minimum problem. 

Got it? It is the same nonsense you wrote. On the ther hand, having
ms_interop is a dynamic thing. You do not have to add it here
manually, because it will be added automatically to the results of the
query fro ms_interop if it is marked as such...

I can think of one reason to use a tracking bug
in addition to the ms_interop keyword: some
of the bugs that lack the ms_interop keyword
nevertheless hinder proper display of MS Office files.
For instance, issue 21393, which sure looks like
it ought to be resolved, even though the engineer
who looked at it removed the ms_interop keyword.

That said, Utomo, there isn't much value in a tracking
bug that just duplicates what you can get from
a query.  If you want people to use and like this
tracking bug, you might need to figure out a
way to make it uniquely useful, e.g. 
"bugs that aren't marked ms_interoperability but
sure look like they should be to me".

JA: changed owner of this issue back to submitter

I didnt have time yet to manage this, so for a moment I will keep this
in the message. so it didnt generate many email 
unless somebody else take care/help.
sorry 

194,834,956,968,1560,1905,2061,2584,2593,3469,3491,3724,4140,4173,4357,4385,4858,4980,4999,5124,5250,5359,5919,6039,6511,6815,7037,7221,7387,7517,7911,8855,9160,9182,9704,9831,9866,9935,10112,10563,10776,10826,10880,10941,11130,11183,11311,11371,11428,11507,11594,11756,11765,11873,11959,11993,12175,12190,12220,12225,12367,12436,12552,12577,12638,12854,12893,12933,13026,13334,13339,13603,13831,13832,13833,13857,13886,13899,13940,14045,14121,14222,14349,14373,14375,14421,14509,14613,14678,14899,14907,14968,14982,14993,15020,15038,15295,15342,15555,15689,15851,15859,15928,16011,16128,16185,16337,16354,16435,16559,16564,16609,16660,16679,16875,16876,16900,16941,16965,16997,17122,17163,17164,17171,17176,17280,17339,17371,17394,17547,17565,17693,17703,17789,17815,17830,18024,18128,18169,18322,18439,18463,18480,18515,18627,18673,18708,18771,19030,19121,19162,19232,19249,19509,19522,19655,19667,19682,19709,19718,19779,19908,19942,19980,20031,20095,20118,20288,20301,20416,20422,20520,20594,20669,20672,20681,20690,20720,20751,20794,20798,20899,20942,20965,20972,21051,21071,21113,21122,21193,21252,21281,21282,21305,21340,21346,21359,21393,21407,21422,21430,21444,21481,21543,21600,21623,21640,21688,21770,21772,21774,21778,22601

WFM

close