_X_t_R_e_s_o_l_v_e_P_a_t_h_n_a_m_e calls _X_t_F_i_n_d_F_i_l_e with the following substitutions in addition to any passed by the caller and returns the value returned by _X_t_F_i_n_d_F_i_l_e:
If a path is passed to _X_t_R_e_s_o_l_v_e_P_a_t_h_n_a_m_e, it will be passed along to _X_t_F_i_n_d_F_i_l_e. If the _p_a_t_h argument is NULL, the value of the _X_F_I_L_E_S_E_A_R_C_H_P_A_T_H environment variable will be passed to _X_t_F_i_n_d_F_i_l_e. If _X_F_I_L_E_S_E_A_R_C_H_P_A_T_H is not defined, an implementation-specific default path will be used which contains at least 6 entries. These entries must contain the following substitutions:
1. %C, %N, %S, %T, %L or %C, %N, %S, %T, %l, %t, %c 2. %C, %N, %S, %T, %l 3. %C, %N, %S, %T 4. %N, %S, %T, %L or %N, %S, %T, %l, %t, %c 5. %N, %S, %T, %l 6. %N, %S, %T
The order of these six entries within the path must be as given above. The order and use of substitutions within a given entry is implementation dependent. If the path begins with a colon, it will be preceded by %N%S. If the path includes two adjacent colons, %%NN%%SS will be inserted between them.
The _t_y_p_e parameter is intended to be a category of files, usually being translated into a directory in the pathname. Possible values might include ``app-defaults'', ``help'', and ``bitmap''.
The _s_u_f_f_i_x parameter is intended to be appended to the file name. Possible values might include ``.txt'', ``.dat'', and ``.bm''.
A suggested value for the default path on POSIX-based systems is
Using this example, if the user has specified a language, it will be used as a subdirectory of /usr/X11R7/lib/X11 that will be searched for other files. If the desired file is not found there, the lookup will be tried again using just the language part of the specification. If the file is not there, it will be looked for in /usr/X11R7/lib/X11. The _t_y_p_e parameter is used as a subdirectory of the language directory or of /usr/X11R7/lib/X11, and _s_u_f_f_i_x is appended to the file name.
The %D substitution allows the addition of path elements to the implementation-specific default path, typically to allow additional directories to be searched without preventing resources in the system directories from being found. For example, a user installing resource files under a directory called ``ourdir'' might set _X_F_I_L_E_S_E_A_R_C_H_P_A_T_H to
The customization string is obtained by querying the resource database currently associated with the display (the database returned by _X_r_m_G_e_t_D_a_t_a_b_a_s_e) for the resource _a_p_p_l_i_c_a_t_i_o_n___n_a_m_e.customization, class _a_p_p_l_i_c_a_t_i_o_n___c_l_a_s_s.Customization where _a_p_p_l_i_c_a_t_i_o_n___n_a_m_e and _a_p_p_l_i_c_a_t_i_o_n___c_l_a_s_s are the values returned by _X_t_G_e_t_A_p_p_l_i_c_a_t_i_o_n_N_a_m_e_A_n_d_C_l_a_s_s. If no value is specified in the database, the empty string is used.
It is the responsibility of the caller to free the returned string using _X_t_F_r_e_e when it is no longer needed.