Apache OpenOffice (AOO) Bugzilla – Issue 26244
No Region Field in Options
Last modified: 2004-03-09 21:01:47 UTC
When trying to utilise the Region (or State) field in Writer, there is no field in Tools / Options to set the field.
Hi, I am not sure if I understand your problem. However does the following help you? Insert -> Field -> Document -> Sender provides "Country" and "State" = Tools -> Options -> OpenOffice.Org -> User Data provides "Country / Region" and "State".
Tools -> Options -> OpenOffice.Org -> User Data provides "Country / Region" and "State". It is on this dialog that I don't have a State text input box. I will attach a screenshot. I am using 1.0.2 and 1.1.0 on RH9 and FC1 respectively. Both installs show the same problem.
Created attachment 13669 [details] No Region/State field is available for editing
Hi, the "State" field only appears on a office with the locale en-US (english USA). Perhaps we should show it also on other locales.
Ah, now i see :-) This is in fact changed with 1.1.1rc1. (I don't know when it was changed, as i couldn't find a DUPL in Issuezilla). -> field "State" exists -> ok -> field "Region" does not exist, because it is handled as a synonym for "Country" (in Insert -> Field -> Document -> there is also only "Country" available). If you would like to have two seperate fields for "Country" and "Region" please file a new request into Issuezilla. This makes it easier to keep things seperate. Thank you for using and supporting OpenOffice.Org! Ok for closing this issue?
Created attachment 13670 [details] attaching sample screenshot from 1.1.1rc1
overlapping entries to this issue, sorry. ------- Additional comments from pb Tue Mar 9 05:15:10 -0800 2004 ------- "Hi,.. <<------>> "Ah, now i see :-) This is in fact changed with 1.1.1rc1. (I don't know.."
>> the "State" field only appears on a office with the locale en-US (english USA). >> Perhaps we should show it also on other locales. hmm, i have linux@linux:~> locale LANG=de_DE@euro LC_CTYPE="de_DE@euro" LC_NUMERIC="de_DE@euro" LC_TIME="de_DE@euro" LC_COLLATE="de_DE@euro" LC_MONETARY="de_DE@euro" LC_MESSAGES="de_DE@euro" LC_PAPER="de_DE@euro" LC_NAME="de_DE@euro" LC_ADDRESS="de_DE@euro" LC_TELEPHONE="de_DE@euro" LC_MEASUREMENT="de_DE@euro" LC_IDENTIFICATION="de_DE@euro" LC_ALL= and still see the "State" field. (using SuSE 9.0 German, Windowmanager)
SBA->Max: (1) Your System has German locales set. But if your OFFICE is an English one, it has the State field. We don't seperate EN_US and EN_UK Office. (2) The Country/Region string is not connected with TWO fields and never was. There never were and it is not planned either. The slash in the middle of this string just may look like thisbecause the filed "pairs" below are seperated by slashes as well. (3) If you look around the world, there is a lot of "Adress items" one might want to add. Some examples: The middle name, the Russian father's name, further adress info like Appt No, Room No, City district and so on (Not to mention an avereage's person's 2 to 10 Email, Fax and Telephon information. So if any change should be undergone here, think global (and usable) before insisting that there is ONE field the whole world is waiting for. Just my 2 cents. Summarised: (for the US folks: "summarized" :-) There is no hidden Region field and the State field is visible in an English office while it can be set in all other localized offices too. So the initial reason for this issue is not existant. This one will be closed as incvalid. Feel free to send Enhancement requests about further fields or the "state" field being visible for all other languages too.
SBA: Closed.
Hello, I logged what I thought was a DEFECT (#id=26244) but have been told it was done on purpose and I need to log an ENHANCEMENT to resolve my issue. The fact that the State field is considered an '"Adress items" one might want to add' - I would say pretty much every country in the world have provinces and states that they need to refer to when corresponding. I don't think 'Russian father's name' is any comparison to a world-wide state field. So I'm going to 'think global (and usable)', open up my atlas and discover that the rest of the world use states too, so I insist that it should be included with the other languages apart from EN_US. (you'll find my new ENHANCEMENT on #26273) Thanks for your time.